When a new version is out
Tori checks for a new release when it opens and every six hours after, and when there is one shows Update available in the title bar.
- Click Install. Tori downloads the build for your Mac and the pill counts up, Updating 40%.
- Before it replaces anything, Tori checks the download is signed by Tori’s team, passes Gatekeeper and is the version the release names. A download that fails any of these is thrown away and the running Tori is left alone.
- Click Restart to update. Tori reopens on the new version.
- Click Update available to open that release’s page on GitHub, with its notes and downloads.
- Click the x to dismiss the notice.
To check right away, choose Tori > Check for Updates… in the menu bar. It says so when you are up to date or when GitHub cannot be reached, and brings the notice back if you dismissed it. Help > Release Notes opens the changelog.
Nothing installs without your click. Where Tori cannot replace itself the pill says Can’t install here instead, and its tooltip says why: Tori is running from the DMG, or from a folder it cannot write to. Drag Tori into Applications and open it from there.
Your sessions keep running through an update: the old daemon holds them and moves to the new version once none is working. See Updates for the pill that shows while it waits.
Builds up to 26.1022
Those builds cannot update themselves. Install the next release once by any
route on Install: the one-line installer, Homebrew
(brew upgrade --cask tori) or the DMG. From then on, Install in the title
bar does it.
Your settings, sessions, spaces and everything under ~/.config/tori/ are kept
across updates.
When Tori closes on its own
If Tori crashes, it writes a crash file under ~/.config/tori/crashes/: the
version, the thread, the error and a backtrace. An uncaught error in the window
is written there too.
The next launch says so: Tori closed on its own 2 minutes ago. A crash file was written., with Reveal, to show the file in Finder, and Report.
Report opens the bug form on GitHub in your browser, filled in with the crash, for you to read and submit. Nothing is sent anywhere without that click, and you can edit or remove anything before submitting.
Crash logs in Settings
Settings > Advanced > Crash logs lists every crash file and shows the version you are running. With none, it says No crash files. If Tori ever closes on its own, the next launch says so and the file lands here. Report a bug opens the same prefilled form.
Reporting anything else
Use Report a bug in Settings > Advanced or Help > Report an Issue in the menu bar, or open an issue on GitHub. Help > Tori Documentation opens these docs. The version you are running is at the top of the Crash logs section.