# Android push identity deletion candidate — 26 October 2026 Based on release 0.6.5, commit 8aa15b286c16ed44c18f59b989dcfbe5b4577b90. This branch is NOT a released version, has no new APK/AAB, and must not overwrite the published 0.6.5 source archive. The installed 0.6.5 stop() starts FCM token deletion without awaiting its result and does not explicitly delete the Firebase installation ID. This candidate removes local background credentials immediately, disables auto-init, cancels notifications, waits for any already-started token requests, waits for token deletion, and then requests installation deletion even if token deletion fails. A failed or timed-out step rejects stop(); the existing JavaScript account-erasure marker remains so cleanup can be retried before another account is opened. Vault/key deletion still proceeds independently of network success. New configure calls are rejected while erasure is pending. Generation checks prevent late configure completions from reporting success or publishing a token after stop. All token requests started through configure are tracked, not just the last one. Network-dependent waits run on the existing single push worker, not the UI thread. Each wait is bounded at 30 seconds. Timeout is failure, not evidence of remote deletion. No SDK upgrade or global version replacement is involved. Google's FirebaseMessaging documentation explicitly distinguishes deleting an FCM token from deleting its Firebase installation ID. The current app uses the token-based API, not the opt-in FID-addressed registration mode. An API success is not proof of instantaneous physical removal from every provider backup. Sources checked 26 October 2026: - https://firebase.google.com/docs/reference/android/com/google/firebase/messaging/FirebaseMessaging - https://firebase.google.com/docs/projects/manage-installations - https://firebase.google.com/support/privacy Before release: native tests with an isolated synthetic identity for successful deletion, network failure and retry, restart with the pending marker, and configuration completing after stop; verify normal new-account push registration afterwards. Do NOT delete Martin_R or rabbi1384 for this test. Existing 0.6.5 phone accounts, installations and coordination remain untouched. Compilation and existing JavaScript erasure-boundary test results are recorded in the separate Store preparation package. Compilation alone is not native erasure QA. Merge only after review, increment to the next available version/code, rebuild and sign, then retain both the old release source and new evidence.