The check dropped every per-server failure and showed one generic
message. It now lists each machine with its reason (sign in first, a
feed key this app does not trust, a timeout), and an APK signed with
another certificate than the installed app is named plainly with how
to install it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Like Linux, the macOS app downloads the verified archive, unpacks it with
ditto beside the installed bundle, swaps it in (keeping the previous
bundle to roll back) and relaunches once the old process has quit.
Each installation generates a private Ed25519 key once (0600, under
~/.config/pipelines), signs version.json with a detached version.json.sig
when publishing APK and desktop builds, and embeds its own and listed
trusted public keys in app builds. The app verifies the feed signature
before trusting the artifact sha256, refuses unsigned or foreign feeds when
it has keys, and requires the sha256 and Android signer in signed feeds.
The Linux app now downloads the release archive to a temporary folder,
verifies its checksum, extracts it beside the install folder, swaps the
bundle in with two renames (keeping <install>.previous for rollback) and
relaunches. A read-only install location is reported with how to fix it.
The prompt and Settings button say "Install and restart".