[Due for payment 2026-09-03] Report changes from expense details thread to expense report after navigating via arrows

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.62-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98611
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two reports with one expense each without category.
4. Go to Home
5. Click Review 2 expenses in For You section.
6. Click Next arrow button.
7. Click Previous arrow button.

Expected Result:

After navigating to another expense via arrow button, report will not change.

Actual Result:

After navigating to another expense via arrow button, report changes from expense details thread to expense report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7243792_1787791856719.10.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7243792

Issue Owner

Current Issue Owner: @thelullabyy

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/32b154b535b2e7d6fde931b28d0cf98db8be10ae30f4647f9ed062ef5f6ee423

[melvin-bot]

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

[melvin-bot]

@JS00001 @ShridharGoel you have been assigned to this deploy blocker because you reviewed the offending PR: #98611

[melvin-bot]

@thelullabyy you have been assigned to this deploy blocker because you authored the offending PR: #98611

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