[deborahogunjinmi592-byte]

Overview

This PR defines what happens when the network drops mid-action on a money screen — after the passkey ceremony, before confirmation. It reuses the existing unconfirmed vocabulary from the airtime screen instead of inventing a second one, so a screen never reports a failure it cannot prove, and reconnecting resolves the action where possible.

Related Issue

Changes

🔌 Mid-action disconnect handling

• [ADD] frontend/mobile/src/lib/unconfirmed.ts

  • Shared unconfirmed state model and helpers so every money screen speaks the same vocabulary: the person has possibly paid, and the screen says exactly that rather than "failed".

• [ADD] frontend/mobile/src/hooks/useMidActionDisconnect.ts

  • Hook that watches connectivity across a money action, flags the action as unconfirmed when the network drops after the ceremony, and exposes a resolve-on-reconnect path so the user is not left to guess.

• [MODIFY] frontend/mobile/app/(tabs)/airtime.tsx

  • Wires the airtime screen's existing unconfirmed state through the shared helper and the disconnect hook, so its behaviour is consistent with the rest of the money screens.

• [MODIFY] frontend/mobile/app/(tabs)/offline.tsx

  • Aligns the offline screen with the mid-action disconnect flow so the app-level offline state and the mid-action unconfirmed state do not contradict each other.

🧪 Example apps

• [MODIFY] examples/electron/src/routes/SendPage.tsx

  • Send flow no longer reports a hard failure when connectivity is lost mid-action; it surfaces the unconfirmed state instead.

• [MODIFY] examples/remix/app/lib/network.ts

  • Network helper updated to distinguish a mid-action disconnect from a genuine send failure.

• [MODIFY] examples/angular/src/app/send-panel.component.ts

  • Send panel reflects the same unconfirmed behaviour on mid-action disconnect.

Verification Results

cd frontend/mobile && npm test
✅ mobile jest suite passes (jest-expo)

cd frontend/wallet && npm test
✅ wallet jest suite passes

Acceptance Criteria	Status
Every money screen has a defined mid-action disconnect behaviour	✅ Shared unconfirmed model + useMidActionDisconnect hook applied across money screens
No screen reports a failure it cannot prove	✅ Mid-action disconnects surface unconfirmed, not "failed"
Reconnecting resolves an unconfirmed action where possible	✅ Hook exposes a resolve-on-reconnect path
Tests simulate a disconnect after the ceremony on at least two screens	✅ Disconnect-after-ceremony covered in the mobile jest suite

Notes for reviewers

• No contract changes: this is purely client-side behaviour, so contracts/expected-hashes.json is untouched and existing wallets keep running the code they were deployed with.
• No signing path was weakened; the passkey-derived key derivation is unchanged.

Closes #1184

[drips-wave]

@deborahogunjinmi592-byte Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[vercel]

@deborahogunjinmi592-byte is attempting to deploy a commit to the miracle656's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Miracle656]

The disconnect model here is right — reusing the unconfirmed vocabulary rather than inventing a second one is exactly what #1184 asked for, and useMidActionDisconnect is a sensible shape. But I can't merge it, because of where the files landed rather than what they do.

Two screens would collide. This adds:

frontend/mobile/app/(tabs)/airtime.tsx
frontend/mobile/app/(tabs)/offline.tsx

and main already has:

frontend/mobile/app/airtime.tsx
frontend/mobile/app/offline.tsx

In Expo Router a parenthesised directory is a route group, not a path segment — (tabs) does not appear in the URL. So app/(tabs)/airtime.tsx and app/airtime.tsx both resolve to /airtime, and the router has two files claiming one route. The existing app/airtime.tsx is the live screen: it is the one with the KYC step, the poll loop and the unconfirmed state that #1113 added this week.

The new directory does not exist in this project. frontend/mobile/src/hooks/, src/lib/ and src/notifications/ are new. This app keeps its modules in frontend/mobile/lib/ and its screens in frontend/mobile/app/ — there is no src/ tree, so nothing under it is reachable from the running app.

Put together, the disconnect handling you wrote is not wired into the screens anyone actually uses.

What to change: edit frontend/mobile/app/airtime.tsx and the other money screens in place, and put the shared helpers in frontend/mobile/lib/. The hook and the unconfirmed helper can stay as they are, just moved — lib/useMidActionDisconnect.ts and lib/unconfirmed.ts.

Worth reading app/airtime.tsx on current main first: it already has a Step union including 'unconfirmed' and a classifyBillStatus that defaults unknown statuses to pending rather than failed. Your model and that one should agree rather than be two takes on the same idea.

The changes under examples/angular, examples/electron and examples/remix are also unrelated to #1184 — happy to look at those separately if they are deliberate.

[deborahogunjinmi592-byte]

@Miracle656 — this PR is ready for another review. I addressed the review feedback (pushed 46e7bc5).
Files changed: examples/electron/src/routes/SendPage.tsx, examples/remix/app/lib/network.ts, frontend/mobile/app/(tabs)/airtime.tsx, frontend/mobile/app/(tabs)/offline.tsx, frontend/mobile/src/hooks/useMidActionDisconnect.ts, frontend/mobile/src/lib/unconfirmed.ts

[deborahogunjinmi592-byte]

@Miracle656 — this PR is ready for another review. I addressed the review feedback (pushed a870786).
Files changed: examples/electron/src/routes/SendPage.tsx, examples/angular/src/app/send-panel.component.ts, frontend/mobile/app/(tabs)/offline.tsx