Android: TWA activities only in the TWA build, push wakes run the bundled app, the origin fails closed; 1.9 (code 10).

2026-10-05T06:02:15Z

F-Droid review of 1.8: the shared manifest declared the TWA's LauncherActivity/IntentActivity in the webview and fdroid builds, which don't compile them (a second, crashing launcher icon). They move to src/twa/AndroidManifest.xml. WakeJob's off-screen WebView now answers the origin from assets like MainActivity's, and Assets returns 404 for any v3.coinos.io path it doesn't carry outside the live API list instead of fetching it. POST_NOTIFICATIONS is asked only when a UnifiedPush distributor is installed. The description names the third-party hosts (DoH, post media). Co-Authored-By: Claude Opus 5.5

A second Android build that can wake the wallet, because it holds it.

2026-09-12T17:32:01Z

The TWA can't. Chrome renders the site, so the wallet's keys live in Chrome's storage for its own origin, and nothing outside Chrome can reach them — a UnifiedPush message could raise a notification and no more. On a phone with Google Play Services none of this matters; without it, background answering was simply unavailable. So: a second flavour, io.coinos.webview, "Coinos (UnifiedPush)". The wallet runs in a WebView this app owns, which means a push can start it off-screen and let it answer for itself. WakeService loads it with ?wake= into the same storage the visible app uses, the page subscribes and answers whatever the payload was about, then calls CoinosHost.done() so the service stops — capped at 25 seconds from the page and 30 from the service, because nothing here is allowed to sit in the background costing battery. Its foreground notification says what it's doing rather than apologising for existing. The WebView carries what the wallet actually needs: DOM storage and IndexedDB, the camera for the QR scanner (granted only once Android has granted it to us), a file chooser for attaching pictures, and links to anywhere but coinos.io handed to a real browser. The trade is named in the code and worth naming here: a separate app is a separate wallet. Its storage is its own, so signing in there is signing in again. That's why this is a second build rather than a replacement — the TWA is untouched, still the better browser for anyone whose phone has push. The shared push receiver now asks the system for whatever front door this build has, and asks a per-flavour Wake class whether the wallet can be woken at all — no flavour checks in the middle of it. Both APKs build and ship: coinos.apk as before, coinos-unifiedpush.apk beside it. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_019mrt228Upn9nNCwGixzSLx

coinosv3.git/android/app/src/twa, branch fdroid-v1.9

Android: TWA activities only in the TWA build, push wakes run the bundled app, the origin fails closed; 1.9 (code 10).

A second Android build that can wake the wallet, because it holds it.