[Due for payment 2025-11-28] [Due for payment 2025-11-26] [RCA #72413] Expense - Infinite loading when member of workspace opens expense created by admin

[jponikarchuk]

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.60-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-2009/folder/13176686/41236628/1022756569
Email or phone of affected tester (no customers): ibellicotest+2082@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Have two accounts opened on two different devices or environments.
Prerequisite 2: User A has at least one workspace.

1. Open the Expensify app.
2. Open any workspace chat.
3. Tap on header and select "Members"
4. Invite User B to workspace chat.
5. Return to chat.
6. Create a manual expense.
7. As User B, navigate to workspace chat.
8. Open the expense created by User A.
9. Note that infinite loading is experienced.

Expected Result:

Member of workspace chat should be able to open expenses created by admin.

Actual Result:

Infinite loading is experienced when opening an expense as member of workspace chat.

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

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021990822560559257369
• Upwork Job ID: 1990822560559257369
• Last Price Increase: 2025-11-18
• Automatic offers:
• situchan | Contributor | 109584814

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

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

[tgolen]

I can't find anything in the deploy checklist that looks related to this. I'm going to open this up to external to see if someone can find the bug. In the meantime, I will see if I can reproduce this locally and investigate.