[$250] Invited to chat only user can't open expense report from the first try

[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.3.5-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: #79098
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 15 iOS 26.1
App Component: Money Requests

Action Performed:

Preconditions: log in as User A on the secondary device, as User B on iOS

1. As User A, create a workspace
2. User A, navigate to the workspace chat, mention User B and select "Invite to chat only" on the whisper message
3. As User B, navigate to the User A's workspace chat
4. As User A, create an expense in the workspace chat
5. As User B, tap on the report preview to open the details

Expected Result:

User B is able to open the expense report from the first try

Actual Result:

When User B opens the report from User A for the first time, it shows skeleton loading, then User B is dropped back in the workspace chat

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7054393_1768956893346.exites_report.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022013796444543651008
• Upwork Job ID: 2013796444543651008
• Last Price Increase: 2026-01-28

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @MarioExpensify

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #79098

[melvin-bot]

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

[melvin-bot]

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

[carlosmiceli]

@parasharrajat @DylanDylann this is probably related to the latest PR: #79299