Files
pipelines/app/notes/startup-update-check.md
T

49 lines
3.0 KiB
Markdown

# Startup and foreground update check
The single `PipelinesApp` session checks the platform's own feed when it opens
and when it returns to the foreground. Web compares the compiled
`PIPELINES_WEB_BUILD_ID` with `/release.json` on the page's origin, even when
its RPC server lives elsewhere. Android compares its installed version code
with the existing Settings APK feed. Appearance never selects the platform.
The web release metadata/install support is the companion manager-owned change
`f05ad62e`; it must land before publishing this client.
Web offers Refresh and Android offers Download, with Later on both native
Material and Cupertino dialogs. Nothing reloads or downloads without consent.
Android uses the existing Settings installer, shows download progress and
reports user-requested install failures. Unavailable, signed-out, malformed and
offline checks stay quiet; a subsequent foreground visit can retry. Feed reads
have a 15-second timeout and never gate the application UI.
Checks coalesce within a foreground visit and offered releases are remembered
for the application session. Endpoint changes are observed so Android also
checks after saved server configuration becomes available. Missing installed
version/build identity skips the comparison rather than guessing an update.
Focused tests and browser evidence will be recorded below after verification.
## Verification
16 focused tests passed (`/tmp/memwatch/out.laN5Vl`) across update parsing,
feed/platform routing, per-visit/per-version behavior and full-app startup flows.
The app regressions cover a saved endpoint arriving later, a server switch while
an old APK lookup is pending, offline startup followed by foreground retry,
consent before refresh/download, and Android progress plus surfaced failures.
The stale-feed guard runs again after consent, before installing anything.
Analyzer clean (`flutter-analyze.U1eqhg`).
The full-app fake-gateway web fixture was built with
`PIPELINES_WEB_BUILD_ID=web-fixture-current` and served a same-origin
`release.json` naming `web-fixture-new`. Browser interaction verified Material
Later dismissal and Cupertino Refresh actually reloads the document (a JS
sentinel was cleared). Captures under `/tmp/review/startup-update-material-repaint`
and `/tmp/review/startup-update-cupertino-final` were inspected. Material required a one-pixel viewport resize and restoration
to force software Chrome to include unchanged canvas layers in the initial PNG.
The repainted capture shows the full dialog and intact shell. Fixture appearance
uses a URL-only parameter, so the refreshed fixture returns to its default host;
production appearance settings are unchanged. The static fixture intentionally
keeps serving the old compiled build, so its update prompt recurs after reload.
Both private browser/server processes are awaited by the capture driver.
No production session, APK feed, or device was changed. Real Android download and
installer behavior remain unverified without an authorized connected test device.