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
Reports - Magic code page opens after selecting option from dropdown button #81235
Version Number: 9.3.11-23 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13176670/test-cases/41237099?p=2 Email or phone of affected tester (no customers):sidnjosdnjdosijsojns@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Search
Action Performed:
Precondition:
Account is unverified.
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Reports > Expenses.
Select the expense via checkbox.
Click dropdown button > Move expense.
Click RHP back button.
Expected Result:
RHP will close.
Actual Result:
Magic code page opens.
The same issue when user clicks Hold, Split, Delete and Merge button from the dropdown.
If account is verified, Add bank account RHP will open instead of magic code.
👋 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.
This PR modifies the KYCWall component navigation logic and affects how unverified users interact with bank account setup flows. The PR was merged on 2026-02-02 and is included in version 9.3.11-23 where this bug appears.
Labels: DeployBlockerCash should remain. This is a frontend bug in the App requiring changes to src/components/KYCWall/BaseKYCWall.tsx or src/pages/Search/SearchSelectedNarrow.tsx.
📋 Detailed Analysis
Evidence
Bug appeared in version 9.3.11-23 on staging (not in production)
PR modifies src/components/KYCWall/BaseKYCWall.tsx which is used by SearchSelectedNarrow
The QA steps in PR fix: 65912 NIT fixes #79343 specifically test similar navigation scenarios with RHP back button behavior (Scenario C, step 6)
Verification
The bug occurs in SearchSelectedNarrow.tsx when:
User selects expenses from Reports > Expenses
User clicks dropdown options (Move, Hold, Split, Delete, Merge)
User clicks RHP back button
Instead of closing RHP, magic code page (ROUTES.ENABLE_PAYMENTS) opens
SearchSelectedNarrow.tsx lines 60-67 shows the KYCWall is configured with enablePaymentsRoute=ROUTES.ENABLE_PAYMENTS which is the magic code page.
Root Cause
PR #79343 modified KYCWall navigation logic in src/components/KYCWall/BaseKYCWall.tsx. When an unverified user interacts with the KYCWall, the component continueAction function checks wallet status and navigates to enablePaymentsRoute (the magic code page).
The issue is that this navigation is being triggered when clicking the back button from dropdown action pages, rather than just closing the RHP as expected. The KYCWall navigation logic is interfering with normal back navigation for unverified users.
Additionally, the addBankAccountRoute parameter uses Navigation.getActiveRoute() which may be capturing the wrong route context and contributing to unexpected navigation behavior.
Activity
melvin-bot commentedon Feb 3, 2026
Triggered auto assignment to @sonialiap (
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 commentedon Feb 3, 2026
Triggered auto assignment to @Julesssss (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 3, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 3, 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 Feb 3, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #79343 - "fix: 65912 NIT fixes" by @MrMuzyk (High confidence)
Related Issues: #79317, #79318, #79323, #79252
Recommendation: REVERT
This PR modifies the KYCWall component navigation logic and affects how unverified users interact with bank account setup flows. The PR was merged on 2026-02-02 and is included in version 9.3.11-23 where this bug appears.
Labels: DeployBlockerCash should remain. This is a frontend bug in the App requiring changes to src/components/KYCWall/BaseKYCWall.tsx or src/pages/Search/SearchSelectedNarrow.tsx.
📋 Detailed Analysis
Evidence
src/components/KYCWall/BaseKYCWall.tsxwhich is used by SearchSelectedNarrowVerification
The bug occurs in SearchSelectedNarrow.tsx when:
SearchSelectedNarrow.tsx lines 60-67 shows the KYCWall is configured with enablePaymentsRoute=ROUTES.ENABLE_PAYMENTS which is the magic code page.
Root Cause
PR #79343 modified KYCWall navigation logic in src/components/KYCWall/BaseKYCWall.tsx. When an unverified user interacts with the KYCWall, the component continueAction function checks wallet status and navigates to enablePaymentsRoute (the magic code page).
The issue is that this navigation is being triggered when clicking the back button from dropdown action pages, rather than just closing the RHP as expected. The KYCWall navigation logic is interfering with normal back navigation for unverified users.
Additionally, the addBankAccountRoute parameter uses Navigation.getActiveRoute() which may be capturing the wrong route context and contributing to unexpected navigation behavior.
MrMuzyk commentedon Feb 3, 2026
Working on a fix
srikarparsi commentedon Feb 3, 2026
Requested CP to staging for the PR
Julesssss commentedon Feb 3, 2026
On staging. Can you retest please @jasperhuangg
IuliiaHerets commentedon Feb 3, 2026
@Julesssss not repro on Chrome / v9.3.11-37
Screen.Recording.2026-02-03.at.20.27.02.mp4
melvin-bot commentedon Feb 3, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.