[Due for payment 2026-01-27] Background changes to Reports after verifying account and opening expense row in Inbox

[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.3.3-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77657
Email or phone of affected tester (no customers): yonghongkok2+sjdo2isjnds2od@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• User A has submitted two IOU expenses to User B.
• Perform the steps below as User B.

1. Go to staging.new.expensify.com
2. Open chat with User A.
3. Open the IOU report.
4. Click Mark as paid.
5. Enter magic code.
6. Click Mark as paid.
7. Click on any expense row.

Expected Result:

Background will remain in Inbox after verifying account and opening expense row.

Actual Result:

Background changes to Reports after verifying account and opening expense row in Inbox.

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]

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

[melvin-bot]

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

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

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #77657 - "Super wide RHP" by @collectioneur (High confidence)
Related Issues: None identified

Recommendation: REVERT

This PR introduced a new expense report route (e/:reportID) and verification flow that does not preserve the navigation context (Inbox vs Reports tab). When a user verifies their account from the Inbox tab, the navigation incorrectly returns to the Reports tab context instead of maintaining the Inbox context.

Labels: Keeping DeployBlockerCash as this is a frontend bug affecting the App. No label changes needed.

📋 Detailed Analysis

Evidence

• The issue explicitly references PR Super wide RHP  #77657 in the issue body
• The bug is reproducible only in staging (where PR Super wide RHP  #77657 is deployed), not in production
• The PR was merged on 2026-01-15 and is in the current StagingDeployCash checklist

Verification

I verified that PR #77657 modified the relevant code paths:

• Added new route: EXPENSE_REPORT_RHP (e/:reportID) in src/ROUTES.ts
• Added new screen: EXPENSE_REPORT_VERIFY_ACCOUNT in src/SCREENS.ts
• Created new page: src/pages/home/report/ExpenseReportVerifyAccountPage.tsx
• Modified navigation logic: Changes to MoneyReportHeader.tsx, MoneyRequestHeader.tsx, MoneyRequestReportView.tsx, and multiple other files to support the new Super Wide RHP functionality

Root Cause

The new ExpenseReportVerifyAccountPage.tsx (line 11) navigates back using:

<VerifyAccountPageBase navigateBackTo={ROUTES.EXPENSE_REPORT_RHP.getRoute({reportID: route.params.reportID})} />

This navigation does not preserve the original tab context (Inbox vs Reports). When verification completes, VerifyAccountPageBase.tsx (line 67) calls:

Navigation.navigate(navigateForwardTo, {forceReplace: true});

The EXPENSE_REPORT_RHP route does not include information about which tab the user was on originally, causing the navigation to default to the Reports tab context instead of preserving the Inbox context.

The PR introduced a comprehensive refactoring of expense report navigation to support Super Wide RHP, but did not account for preserving navigation context across the account verification flow when opened from different tabs.