53 lines
3.4 KiB
Markdown
53 lines
3.4 KiB
Markdown
# Native updates from saved machines
|
||
|
||
Android, Linux x64 and macOS clients check all saved logical servers on foreground
|
||
visits and through Settings → App updates. Each machine's aliases are checked
|
||
independently and failed/signed-out addresses do not hide compatible builds found
|
||
elsewhere. The newest numeric build wins; the prompt and manual result name its
|
||
saved machine alias. Native checks never select another server or change its socket.
|
||
Web release checks remain bound to the page origin.
|
||
|
||
Android retains `/updates/version.json` and its APK installer. Linux reads
|
||
`/updates/linux-x64/version.json`; macOS reads `/updates/macos/version.json`.
|
||
Desktop feeds require the matching platform and actual native architecture, and a
|
||
relative artifact basename. Desktop updates download to Downloads and open the
|
||
archive; the running application is never replaced automatically. Build identity
|
||
uses `PIPELINES_NATIVE_BUILD_CODE` when embedded, with package build number as fallback.
|
||
|
||
Each request uses a read-only per-profile credential snapshot, trusted only for its
|
||
explicit HTTP origins. Logout invalidates retained credentials, while removed
|
||
profiles/aliases invalidate retained update offers. Redirects are not followed.
|
||
Metadata is bounded to 64 KiB, requests/streams have deadlines, and a provided
|
||
SHA256 is verified before publishing/opening the download. Failed downloads delete
|
||
partial files. The already locked crypto dependency is promoted to direct use.
|
||
|
||
Verification: focused updater, profile/request auth and startup-flow suite passed
|
||
36 tests after metadata validation, trust invalidation and download integrity checks, including loopback authenticated
|
||
archive integrity success/failure, newest-server selection with an offline peer,
|
||
foreign origin rejection, removed trust, and platform/architecture/path filtering.
|
||
Analyzer clean. Final checks and rendered capture evidence recorded in delivery.
|
||
|
||
Inspected real generic full-app browser captures (no production endpoints):
|
||
- `/tmp/review/native-updates-material/01-native-update-prompt.png` (1280×900 dark Material, Linux)
|
||
- `/tmp/review/native-updates-cupertino/01-native-update-prompt.png` (900×900 light Cupertino, macOS)
|
||
Both show source alias, archive instructions, and working Later action. Browser
|
||
captures validate portable prompt layout; real desktop installer/device behavior
|
||
is not claimed by these captures.
|
||
|
||
Final suite `/tmp/memwatch/out.6XWDNJ`: 36 passed; analyzer clean at
|
||
`/var/folders/jp/q0qvjyg54fl_c5vhhk1ylz2m0000gn/T/flutter-analyze.zQ46R4`.
|
||
Display names subsequently polished to Linux/macOS (feed values unchanged).
|
||
|
||
Manager integration: combined server-selection/creation, updater/session,
|
||
server scopes and chat automation suite passed 89 tests after adding an explicit
|
||
native-update capability override to the Root test host. Existing server-switch
|
||
fixtures disable native network probing; production defaults still enable all
|
||
supported native platforms. This resolved two pending-timer fixture failures
|
||
introduced when Linux became supported. Analyzer clean (9sOpy3).
|
||
|
||
Android feeds may advertise `signingCertificateSha256`. The app rejects malformed
|
||
fingerprints and compares valid ones with `PackageInfo.buildSignature` before
|
||
considering a build, so a newer APK signed independently on another machine does
|
||
not hide an installable peer. Legacy feeds without the field retain Android's
|
||
installer signature validation. Desktop archive feeds are unaffected.
|