Expense - Infinite loading when navigating back to ws chat after merging expense with self-DM

[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: v9.3.0-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning. The user isn't redirected to self DM after merging expenses in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78842
Email or phone of affected tester (no customers): htad26+yewrytwegd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iOS 26.1/iPhone 13
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
   2.Create an expense in self DM.
2. Create an expense in a workspace chat.
3. Open the expense report in the workspace chat.
4. Tap More > Merge.
5. Select self DM expense > Continue.
6. Select all the details from self DM expense (second option in each section) > Next.
7. Tap Merge expenses.
8. After being redirected to Self-DM, tap the Back arrow to return to the workspace chat.

Expected Result:

The user is navigated back to the workspace chat successfully, and the chat loads normally.

Actual Result:

Infinite skeleton loading is displayed

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

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

[francoisl]

Running an ad-hoc build for a revert of PR 79275 here: #79505 though it I'm not confident that was the issue, or at least it doesn't make sense it only occurs on iOS.