Reports - Magic code page opens after selecting option from dropdown button

[mitarachim]

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

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Go to Reports > Expenses.
5. Select the expense via checkbox.
6. Click dropdown button > Move expense.
7. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7064876_1770088190711.1.mp4

View all open jobs on GitHub

[melvin-bot]

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]

Triggered auto assignment to @Julesssss (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.

[OSBotify]

🔍 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

• Bug appeared in version 9.3.11-23 on staging (not in production)
• PR fix: 65912 NIT fixes #79343 was merged on 2026-02-02 and is included in this version
• 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:

1. User selects expenses from Reports > Expenses
2. User clicks dropdown options (Move, Hold, Split, Delete, Merge)
3. User clicks RHP back button
4. 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.