[Due for payment 2026-07-06] [Due for payment 2026-07-02] [Due for payment 2026-07-01] Android - IOU - App crashes after mark as paid and view IOU offline

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.4.18-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-48123/folder/13176679/41237858/1512014884?sort=%2Bidentifier
Email or phone of affected tester (no customers): leungbratt6+2406@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Pixel 7 Pro/Android 17
App Component: Chat Report View

Action Performed:

Precondition: Another user creates an IOU to the main device

1. Open the Android app
2. Navigate to the 1:1 DM
3. Go offline
4. Locate the IOU -> Mark as paid on the preview
5. Tap on the View button on the preview

Expected Result:

App not crash

Actual Result:

App crashes

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7189236_1782266464643!log.txt

Bug7189236_1782266464644.crash.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7189236

Issue Owner

Current Issue Owner: @aimane-chnaif

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/6afbaba81ab0f8535197a868441a745d33e02d9063821bf321dc91a0ae49c1e0

https://platform.applause.com/services/links/v1/external/1086377157d01694ba5c675b571cc277e624fef2e925f5538b032147aa206072

[melvin-bot]

Triggered auto assignment to @puneetlath (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[mitarachim]

Issue not reproduce while Use Staging Server is disable/OFF

2026-06-24.11.44.51.AM.mp4

[MelvinBot]

⚠️ Preliminary analysis — the user-flow and regression window are confirmed, but the exact crashing frame still needs the Android stack trace. Treat the root-cause section as the leading lead, not a settled conclusion.

Issue Analysis

What we know for sure: This is a render crash, not a navigation crash. On an Android phone (small screen), tapping View on the money-request preview calls openReportFromPreview, which navigates to the full IOU report via ROUTES.REPORT_WITH_ID — MoneyRequestReportPreviewContent.tsx. On wide layouts it instead opens the lighter EXPENSE_REPORT_RHP, which is why this reproduces on Android app but not desktop/mWeb. The crash happens while rendering that IOU report, which now contains the freshly-added optimistic PAY action and an optimistically-settled (REIMBURSED) report from the offline mark-as-paid.

Regression window: Reproducible in staging v9.4.18-0 but not production v9.4.17-3, so it was introduced this release cycle.

Leading suspect already ruled out: Expensify/App#94204 (DEW approval, reworks AnimatedSettlementButton) is the most obvious pay-button change in the delta, but it does not explain this crash: its new logic is gated on isDEWApproval && isApprovedAnimationRunning — both false in a 1:1 DM pay flow (no policy, paid ≠ approved) — and its one new unconditional code path, the getMostRecentActiveDEWApproveFailedAction selector, is fully null-safe (ReportActionsUtils.ts:371-393). So the culprit is most likely another v9.4.18 change on the IOU-report render path.

Recommended next step (deploy blocker): Pull the Android crash group for build 9.4.18-0 from Crashlytics/Sentry (App project, Android, react-native) and read the top JS frame — that will pin the introducing PR in minutes. I couldn't query Sentry from this run (no credentials / OAuth in this environment).

Candidate render-path files changed between 9.4.17-3 and 9.4.18-0-staging

Diff scope: gh api repos/Expensify/App/compare/9.4.17-3...9.4.18-0-staging. Files on the opened-IOU-report render path worth bisecting against the stack trace:

• src/components/ReportActionItem/MoneyRequestView.tsx (+38/-6) — renders the transaction inside the opened report; new useSplitEffectivePolicy / useRestrictedActionPolicyID hooks and a changed transaction derivation.
• src/pages/inbox/report/ReportActionItem.tsx (+9/-4)
• src/components/SettlementButton/AnimatedSettlementButton.tsx (+53/-2) — Fix - Blocked DEW Report Approval Briefly Shows “Approved” State Before Reverting #94204 (ruled out above, but verify against the trace).
• src/components/MoneyReportHeaderPrimaryAction/PayPrimaryAction.tsx, .../PayActionButton.tsx — Fix - Blocked DEW Report Approval Briefly Shows “Approved” State Before Reverting #94204.

Confirmed flow evidence:

• View button → openReportFromPreview: ReportPreviewActionButton.tsx:232-238
• Small-screen navigates to REPORT_WITH_ID: MoneyRequestReportPreviewContent.tsx:516-536
• Optimistic mark-as-paid mutations (nulls chatReport.iouReportID, adds PAY action, sets REIMBURSED): PayMoneyRequest.ts:292-342
• Opened report resolves a one-transaction thread to CONST.FAKE_REPORT_ID when no real thread exists (an unverified-but-plausible crash locus): ReportActionsUtils.ts:1957-1963

---

Next Steps for Contributor+ team:
To pin & fix: grab the Android 9.4.18-0 stack trace, then reply @MelvinBot implement [this] once the introducing PR/line is confirmed.
To refine: @MelvinBot <your feedback> (e.g. paste the Crashlytics/Sentry stack trace and I'll pinpoint the line).
To reject: Explain why you are rejecting this analysis.