[bmc08gt]

When a user says they aren't getting notifications, there's nothing on the phone that tells them, or us, which part is broken: the permission, a blocked channel, battery optimization, or push registration with Flipcash. This adds a status page at Settings › Advanced › Notifications that runs those checks, offers a fix for each one that fails, asks Flipcash to send a test notification, and shares a plain-text report for support.

Spec: code-payments/flipcash-client-orchestrator#73 (Android and Both items). Figma page 12952:56; S5 is the Android frame.

Checks and registration

• New features/notification-status module. The status model is a pure function from a device snapshot plus the last registration record to rows and a summary, with no Android types. The device read is the only Android-facing part.
• Android checks a1–a7: permission, per-channel and group blocks, other categories, battery optimization, background restriction plus standby bucket, and Play services.
• PushRegistrar in authentication records each AddToken attempt per account, with the time of the last ok, and clears the record on logout. Login, token refresh and the status page all go through it. If the page closes mid-attempt, or the timeout fires before a token is fetched, nothing is saved.
• AddToken has no deadline and waits for ready, so in airplane mode it never returns. The registrar applies its own 10 s timeout at every call site and classifies timeouts, UNAVAILABLE and IO failures as "Couldn't reach Flipcash" rather than "Registration failed". That row is a Warning reading "Last confirmed " when an earlier ok is on record, and a Fail otherwise.
• FirebasePushTokenProvider.deleteToken() now waits for the delete to finish, so Try again can't get the old token back.
• All six channels and both groups are created at app start instead of on first post, so a channel a user has never received can still be checked.

Page

• Rows start as Checking and change in place with a crossfade, so nothing jumps while checks run. A finished Fail or Warning sets the summary even while registration is still checking, and the summary's "Checked just now" line appears once the first run finishes.
• A failing row puts the failure in its title and the explanation in the detail line. The all-pass fold and the rows hidden when the permission is off both animate.
• A refresh icon in the top bar ("Check Again") re-runs every check, including a fresh AddToken. It's disabled while a run is in progress. Rows keep their titles and fix pills during the run; the pills are disabled until the row's result is in. The folded "N checks passed" row keeps its title and only its mark shows Checking. The summary card keeps the previous run's summary (e.g. "1 thing to fix") until the new run finishes, then animates to the new one. The same holds for Try Again on the registration row and the re-run after Turn On is granted; "Checking…" shows only on the first run after the page opens.
• Coming back to the foreground re-reads only the phone's settings. Registration keeps its last result, so a folded page doesn't unfold and refold; it runs again only on open and on Check Again.
• Each row reserves two lines of detail, Checking included, so a result that wraps doesn't push the rows below it.
• At a font scale of 1.5 or more (the threshold UserLinkCard uses), the footer buttons scroll with the page instead of staying pinned.
• Send Test Notification calls PushController.sendTestPush() with a 10 s timeout and shows loading while it's in flight. The server sends "Test Notification" with an empty payload, which NotificationService posts on the general channel (fcm_fallback_notification_channel, shown as "Misc.") with no navigation. The button is disabled while notifications or that channel are off, with a line under it saying which to turn on.
• When the in-app Turn On is granted, every check runs again, registration included.
• On success the button becomes Send Again and the floating toast host shows "Test notification sent" with a check icon. A timeout or transport failure shows "Couldn't reach Flipcash"; any other failure shows "Couldn't send a test notification". The footer says Flipcash sends the test to every phone signed in to this account.
• Share Report's registration line describes this page's latest run. A run that saved nothing reads <status> (<reason>), e.g. fail (noToken), rather than an older record from login; a run still going reads checking. A Last ok: <time> line (or never) follows it.
• Scroll edges use TopScrollEdge/BottomScrollEdge over haze, matching Settings. Group headers use SectionHeader in title case ("On This Phone", "With Flipcash"), as are the buttons.

Theme

• New warningText colour token, named to match successText/errorText (the spec calls it textWarning). Flipcash uses the existing Flipcash2ColorSpec.warning (#FFA953); the Code theme uses Warning.

Copy not in the spec

• The spec gives a2 copy for chat only. Deposit, buy/sell, gain and general channel rows use the same " notifications are off" pattern; the strings are in apps/flipcash/core strings.xml.