diff --git a/docs/notes/two-machine-install-checklist.md b/docs/notes/two-machine-install-checklist.md index 5465f578..771bced1 100644 --- a/docs/notes/two-machine-install-checklist.md +++ b/docs/notes/two-machine-install-checklist.md @@ -30,3 +30,18 @@ smoke test used a private HOME/config/database and no model inference. Linux systemd login startup and installation on the operator's Linux computer remain for that physical-machine test; successful Docker client compilation does not verify either. No Android device was connected during this release preparation. + +## Sharing Android updates between machines + +Android updates must use the signing identity of the app already installed. +New APK feeds report the certificate fingerprint; the client skips advertised +mismatches even if their build number is higher. Old feeds without fingerprints +retain their legacy behavior and Android still validates installation. + +To offer the same phone app from both machines, copy the published +`lib/app-updates/pipelines.apk` and matching `version.json` to the second server's +`lib/app-updates/` (publish the APK before its feed). These are distribution files, +not signing keys or provider credentials. A separately generated Linux signing +key cannot update a phone app signed by the Mac key. Keep the existing phone app +and its data; it can still connect to both server profiles regardless of where +its APK was built.