88685262ce
The injected MainActivity overrode Capacitor's WebViewClient, wiping out the client Capacitor needs to load the web layer — causing a black-screen crash on launch. Remove the MainActivity template, its injection script, and the build wiring. The real signing fix (setPackageName before signEvent) is unaffected and remains in place. Bump to 1.2.10. Co-authored-by: shakespeare.diy <assistant@shakespeare.diy>
35 lines
1.4 KiB
Text
35 lines
1.4 KiB
Text
v1.2.10
|
|
|
|
🛠️ Fixes a startup crash (black screen) introduced in the previous build and
|
|
keeps the Amber signing fix: signing now opens Amber the same reliable way
|
|
login does, so delete / accept invite / zap complete instead of hanging.
|
|
|
|
After updating, log OUT and log back IN once.
|
|
|
|
---
|
|
|
|
v1.2.8
|
|
|
|
🛠️ Amber finally pops up — signing works (the real fix)
|
|
The big one. On some Android setups (notably GrapheneOS), tapping delete,
|
|
accepting a crew invite, sending a zap, or editing your profile would spin
|
|
forever and Amber never appeared.
|
|
|
|
Root cause: the app's browser layer was silently dropping the request that
|
|
opens Amber, so the approval screen never launched. We added a native hand-off
|
|
so signing requests now open Amber directly — exactly like login already does.
|
|
|
|
Now every signing/encryption action launches Amber, you approve, and the
|
|
action completes. If Amber genuinely doesn't respond you get a clear message
|
|
in seconds instead of an endless spinner.
|
|
|
|
IMPORTANT: after updating, log OUT and log back IN once. Then delete, accept
|
|
invite, zap, and profile edits will just work.
|
|
|
|
🔔 Notification bell "Mark read" actually clears the badge
|
|
Marking notifications read now clears the count for crew items too, while
|
|
your pending invites and requests stay visible in the Crews tab until you
|
|
act on them.
|
|
|
|
🧹 Housekeeping
|
|
Behind-the-scenes reliability fixes across the signing and notification flows.
|