[Due for payment 2025-09-16] Expense - Report loads infinitely in Inbox after deleting expense on Reports

[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: 9.2.1-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: #66890
Email or phone of affected tester (no customers): sdjdoijsojnsoi@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.expensify.com
2. Create a workspace.
3. Go to workspace chat.
4. Submit an expense to workspace chat.
5. Click on the expense report.
6. Go to Reports > Expenses.
7. Select the expense via checkbox.
8. Click on the dropdown menu > Delete.
9. Delete the expense.
10. Go to Inbox.

Expected Result:

Workspace chat will open in Inbox without issue.

Actual Result:

Report loads infinitely in Inbox after deleting expense on Reports.

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

Bug6933783_1756853603742.Screen_Recording_2025-09-03_at_06.52.16.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @zanyrenney

[melvin-bot]

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

[SzymczakJ]

I'm going to tackle this, as this is one of the preload screens regressions and @WojtekBoman asked me to help him.