[Due for payment 2025-09-22] [Due for payment 2025-09-18] expense-App crashes when adding an unreported expense to a report

[mitarachim]

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.2.9-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-746/folder/13176730/41237114/889703000
Email or phone of affected tester (no customers): Slottwo1 bxvb@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote note 10s android 13
App Component: Money Requests

Action Performed:

Pre-condition: Have an expense in self DM and workspace

1. Launch app
2. Open workspace chat
3. Open a expense - more - add expense - add Unreported expense
4. Add to report

Expected Result:

App must not crash when adding an unreported expense to a report

Actual Result:

App crashes when adding an unreported expense to a report

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6941114_1757564691138!Crash.txt

Bug6941114_1757564039362.Screenrecorder-2025-09-11-09-38-09-674.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @flaviadefaria

[melvin-bot]

Triggered auto assignment to @flaviadefaria (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @Beamanator (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.

[Beamanator]

Wait Reproducible in production?: Yes = maybe this shouldn't be a blocker