A generic update failure creates two problems. The app is still out of date, and nobody knows whether the cause was a temporary download, a damaged archive, or a deeper install issue.
Version 1.3.1 makes that failure state specific enough to act on.
The error now reaches the person
If an interactive update fails, Agent Callout shows the reason in the on-screen message instead of reducing every path to the same failure. The same reason is written to the macOS unified log for a deeper investigation when needed.
Each install stage is logged as it happens, so a report can distinguish fetching, verification, replacement, and relaunch work.
Retry stays one click away
A failed attempt no longer retires the update action. The newer version remains offered in the menu and Settings, making a transient network problem a simple retry instead of a support journey.
The product does not pretend the update succeeded, and it does not punish the person for a recoverable failure.
Product decision
The principle behind 1.3.1
Errors should preserve agency. A good failure state explains what happened, keeps the safe next action available, and records enough evidence to diagnose the cases that do not recover.
We chose a small patch release because this behavior affects trust in every release that follows it.