Live Session app v1.1.23: Find out why an update refused to install
When an update fails, Chief now records the stage it stopped at, and tells you where the app is actually installed when the location is the problem.
Updates that failed used to leave you with nothing to act on. The log noted a new version was available and then went quiet, so five failed attempts looked identical to one.
Update failure details
Chief now records what stopped an update and how far it got, whether it was checking for a new version, downloading it, or verifying it. If you send a support log after a failed update, the cause is in it.
When an update stalls because a previous attempt is still running, that shows up in the log too, instead of leaving later attempts to fail silently.
Install location message
Chief can only update itself when it runs from your Applications folder. The old message told you to drag Chief into Applications without saying where it was running from, which was no help if you had a copy in your personal Applications folder or were running it straight off a mounted disk image.
The message now names the path Chief is running from, so you can see which copy to move.
If an update has failed for you before, this build gives you and support something concrete to work from on the next attempt.