|
|
If session restoration isn't working for you, please check the following:
|
|
|
|
|
|
1. **System Prefs > General > Close windows when quitting an app** is off.
|
|
|
2. **Preferences > General> Startup > Window restoration policy** is **Use System Window Restoration Setting**
|
|
|
3. **Preferences > Advanced > Enable session restoration** is on.
|
|
|
4. You are not using non-native full screen windows. macOS does not support restoring these ☹️
|
|
|
|
|
|
If you've done all this and it still doesn't work, I'll need a debug log that captures info from before restarting and after restarting. Follow these steps:
|
|
|
|
|
|
1. Turn ON **Preferences > Advanced > Append to existing debug log rather than replacing it**
|
|
|
2. Turn ON **Preferences > Advanced > Start debug logging automatically when iTerm2 is launched**
|
|
|
3. Prepare your windows to reproduce the issue. It's best if there is only one window to make the debug log easy to analyze.
|
|
|
3. Wait five seconds. This ensures any recently closed sessions are fully terminated.
|
|
|
4. Select **iTerm2 > Toggle debug logging** to start logging.
|
|
|
5. Type something in the window that you expect to exhibit the bug.
|
|
|
6. Cmd-tab out of iTerm2 and back. This causes the window state to be saved.
|
|
|
7. Kill the app. The easiest way to trigger session restoration is to right click the iTerm2 dock icon and choose **Force Quit**. That's preferred because quitting iTerm2 cleanly will terminate the sessions, and they won't be restored.
|
|
|
8. Re-launch iTerm2.
|
|
|
9. Verify the session was not properly restored.
|
|
|
10. Select **iTerm2 > Toggle debug logging** to stop logging.
|
|
|
11. Attach `/tmp/debuglog.txt` to an issue. You can file issues at https://iterm2.com/bugs |