You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-01-27] Expense report wide RHP closes and it reopens in central pane after clicking header subtitle #79734
Version Number: 9.3.3-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod 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):jsnodsjdosjsoij@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:
Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses.
Open the expense report.
Open any expense row.
Click on the report link in report header subtitle.
Expected Result:
App will return to expense report wide RHP.
Actual Result:
Expense report wide RHP closes and it reopens in central pane.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #77657 - "Super wide RHP" by @collectioneur (High confidence) Related Issues: Original feature issue #71821
Recommendation: REVERT
This PR introduces a major navigation refactor for expense reports. The bug is a regression in the navigation logic that was specifically tested in the PR (Test 6), indicating the logic needs revision before redeployment.
Labels: Keeping DeployBlockerCash (App deploy blocked). Removing DeployBlocker (this is a frontend-only bug, no backend changes needed).
📋 Detailed Analysis
Evidence
PR #77657 was merged on 2026-01-15 at 11:59:59Z and introduced a new "Super Wide RHP" feature for displaying expense reports. The bug was reported on 2026-01-16 and is staging-only, confirming it was introduced in this deploy. Melvin-bot correctly identified this PR as the cause.
The PR explicitly tested this scenario in Test 6: "Click the link below the wide RHP title that leads back to the parent report. Verify that the wide RHP correctly returns back to the parent super wide RHP."
Verification
The bug occurs in navigation logic modified by the PR:
Affected file: src/components/ParentNavigationSubtitle.tsx (48 lines added/12 deleted in PR)
Related files: Navigation system files (Navigation.ts, RightModalNavigator.tsx, etc.)
The PR modifies 64 files across the navigation system, introducing new routes and navigation patterns for super wide RHP.
Root Cause
In src/components/ParentNavigationSubtitle.tsx, the onPress handler has logic to handle navigation from a wide RHP (expense detail) back to a super wide RHP (expense report).
The bug occurs at lines 153-158: When checking if we should navigate to the parent report within the RHP, the code checks if lastRoute?.name === SCREENS.RIGHT_MODAL.SEARCH_MONEY_REQUEST_REPORT. However, lastRoute refers to .at(-1) which is the CURRENT route (SEARCH_REPORT - the expense detail), not the previous route in the stack.
The condition at line 155 evaluates to false because lastRoute is SEARCH_REPORT, not SEARCH_MONEY_REQUEST_REPORT. The more specific check at lines 164-173 also doesn't match because it checks for EXPENSE_REPORT, not SEARCH_REPORT.
As a result, the code falls through to the default navigation (lines 176-179) which uses ROUTES.REPORT_WITH_ID.getRoute(), causing the report to open in the central pane instead of going back to the super wide RHP that was already open.
Expected behavior: The code should check the previous route (.at(-2)) to detect that SEARCH_MONEY_REQUEST_REPORT is already open for this report and simply go back instead of navigating to a new route.
changed the title [-]Expense report wide RHP closes and it reopens in central pane after clicking header subtitle[/-][+][Due for payment 2026-01-27] Expense report wide RHP closes and it reopens in central pane after clicking header subtitle[/+]on Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@ZhenjaHorbach@joekaufmanexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Jan 16, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #77657
melvin-bot commentedon Jan 16, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 16, 2026
Triggered auto assignment to @joekaufmanexpensify (
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 commentedon Jan 16, 2026
👋 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:
OSBotify commentedon Jan 16, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #77657 - "Super wide RHP" by @collectioneur (High confidence)
Related Issues: Original feature issue #71821
Recommendation: REVERT
This PR introduces a major navigation refactor for expense reports. The bug is a regression in the navigation logic that was specifically tested in the PR (Test 6), indicating the logic needs revision before redeployment.
Labels: Keeping
DeployBlockerCash(App deploy blocked). RemovingDeployBlocker(this is a frontend-only bug, no backend changes needed).📋 Detailed Analysis
Evidence
PR #77657 was merged on 2026-01-15 at 11:59:59Z and introduced a new "Super Wide RHP" feature for displaying expense reports. The bug was reported on 2026-01-16 and is staging-only, confirming it was introduced in this deploy. Melvin-bot correctly identified this PR as the cause.
The PR explicitly tested this scenario in Test 6: "Click the link below the wide RHP title that leads back to the parent report. Verify that the wide RHP correctly returns back to the parent super wide RHP."
Verification
The bug occurs in navigation logic modified by the PR:
src/components/ParentNavigationSubtitle.tsx(48 lines added/12 deleted in PR)Navigation.ts,RightModalNavigator.tsx, etc.)The PR modifies 64 files across the navigation system, introducing new routes and navigation patterns for super wide RHP.
Root Cause
In
src/components/ParentNavigationSubtitle.tsx, theonPresshandler has logic to handle navigation from a wide RHP (expense detail) back to a super wide RHP (expense report).The bug occurs at lines 153-158: When checking if we should navigate to the parent report within the RHP, the code checks if
lastRoute?.name === SCREENS.RIGHT_MODAL.SEARCH_MONEY_REQUEST_REPORT. However,lastRouterefers to.at(-1)which is the CURRENT route (SEARCH_REPORT - the expense detail), not the previous route in the stack.Actual navigation stack when bug occurs:
The condition at line 155 evaluates to false because
lastRouteis SEARCH_REPORT, not SEARCH_MONEY_REQUEST_REPORT. The more specific check at lines 164-173 also doesn't match because it checks for EXPENSE_REPORT, not SEARCH_REPORT.As a result, the code falls through to the default navigation (lines 176-179) which uses
ROUTES.REPORT_WITH_ID.getRoute(), causing the report to open in the central pane instead of going back to the super wide RHP that was already open.Expected behavior: The code should check the previous route (
.at(-2)) to detect that SEARCH_MONEY_REQUEST_REPORT is already open for this report and simply go back instead of navigating to a new route.IuliiaHerets commentedon Jan 16, 2026
@mountiny Issue is not reproduced on Web and iOS, build 9.3.3-6
1768583773823.ScreenRecording_01-16-2026_12-15-14_1.mp4
1768583511824.498.mp4
[-]Expense report wide RHP closes and it reopens in central pane after clicking header subtitle[/-][+][Due for payment 2026-01-27] Expense report wide RHP closes and it reopens in central pane after clicking header subtitle[/+]melvin-bot commentedon Jan 20, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-01-27. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 20, 2026
@ZhenjaHorbach @joekaufmanexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]