[Due for payment 2025-07-30] [Due for payment 2025-07-28] Reports - Reports load infinitely after reset app until workspace chat is opened

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

Action Performed:

1. Go to staging.expensify.com
2. Log in with a new account.
3. Create a workspace.
4. Submit an expense in workspace chat.
5. Go to Reports.
   → Reports load fine without issue.
6. Go to Account > Troubleshoot > Clear cache and restart > Reset and refresh.
7. Go to Reports.
   → Reports load fine without issue.
8. Go to Workspaces.
9. Go to Reports.
   → Reports load infinitely.
10. Go to Inbox and open workspace chat if not opened.
11. Go to Reports.
    → Reports load fine without issue after workspace chat is loaded.

Expected Result:

In Step 9, Reports load fine without issue.

Actual Result:

In Step 9, Reports load infinitely after reset app and switching between Inbox and Workspaces when workspace chat is not opened.
In Step 11, Reports load fine without issue after workspace chat is loaded.

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

Bug6891221_1752818864023.20250718_140533.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[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.

[melvin-bot]

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

[melvin-bot]

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