[Epic] Play production crashes vitals triage

[piotr-iohk]

Elevated user-perceived crash rate on mainnet 2.2.0 (181). Tracks Play Vitals triage (Jun 2026).

Vitals: https://play.google.com/console/u/1/developers/5690237613698939049/app/4973032799696771282/vitals/crashes?days=28&isUserPerceived=true

Child issues

high-priority:

• [Bug]: Production SIGABRT in arm64 native code (Play 2.2.0 / build 181) #982 — SIGABRT arm64 (P0 ~38%)
• [Bug]: ForegroundServiceStartNotAllowedException in LightningNodeService.onCreate (dataSync quota, Android 15+) #981 — FGS start not allowed (P0 ~23%)
• [Bug]: ForegroundServiceDidNotStopInTimeException on LightningNodeService (Android 15+, 2.2.0) #980 — FGS did not stop (P0 ~22%)

medium-priority:

• [Bug]: CoreService$init$1.invokeSuspend — UniFFI API checksum mismatch (bitkit-core, Play 2.2.0) #983 — UniFFI checksum (P2)
• [Bug]: $Proxy4.uniffi_ldk_node_fn_free_node — TimeoutException on Node destroy (Play 2.2.0) #984 — free_node timeout (P2)
• Optimise Node Foreground Service #443 — Optimise node FGS
• [Bug]: Node.listBalances ANR in receive flow #1036

Bundles: FGS (#980, #981, #443); native (#982 ± #984). DidNotStartInTime @ MainActivity (3/60d) → #981, no separate issue.

Done

P0 closed; P2 closed/deferred; AAB + native symbols each release; 28-day crash rate improved vs Jun 2026.

[ovitrif]

Milestones:

• 2.3.0 for high priority issues
• 2.4.0 for medium priority issues

[ovitrif]

Update on milestones:
More certainty about fixing #982 requires update across all our Rust repos, won't land in 2.3.0, now targeting 2.4.0.

Work is ongoing but risk of delays for getting PRs in 4 repos merged is too impactful for the upcoming release.