iOS - Expensify card - The Choose a limit type page re-appears briefly

[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: v9.3.16-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: #81357
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 13 iOS 26.2.1, Samsung A25, Android 16
App Component: Workspace Settings

Action Performed:

Workspace is set up with Expensify Card feature.

1. Open the app
2. Go to workspace settings > Expensify Card.
3. Click Issue card.
4. Select a member
5. Select Physical card
6. Select Smart Limit
7. Enter 2 in the Amount field
8. Tap Next

Expected Result:

After Entering a limit type and tapping Next, user is navigated to the Give it a name page, without re-appearing the Choose a limit type page.

Actual Result:

The Choose a limit type page re-appears briefly

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

[melvin-bot]

@cead22 recently merged #81357, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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.

[melvin-bot]

Triggered auto assignment to @grgia (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: #81357 - "fix:80352: Expensify Card - App reopens Expensify Card page after issuing card and swiping right" by @Eskalifer1 (High confidence)
Related Issues: #80352 (the issue PR #81357 was attempting to fix)

Recommendation: REVERT

PR #81357 introduced Navigation.closeRHPFlow() calls that are causing navigation state issues during the card issuance flow. The fix appears to be creating a new problem while solving the original swipe-right navigation issue. Reverting will allow time to find a solution that fixes #80352 without breaking the step-by-step flow.

Labels: No label changes made - keeping DeployBlockerCash as this is a frontend bug blocking the App deploy.

📋 Detailed Analysis

Evidence

• The issue reports that the "Choose a limit type" page (LimitTypeStep) re-appears briefly after entering a limit and tapping Next
• PR fix:80352: Expensify Card - App reopens Expensify Card page after issuing card and swiping right #81357 was recently merged on Feb 6, 2026 and is listed in the current StagingDeployCash issue Deploy Checklist: New Expensify 2026-02-10 #81937
• The issue is marked as reproducible in staging v9.3.16-0 but N/A for production (new feature)
• Melvin-bot auto-assigned the PR author @cead22 (though they are OOO) in the issue comments

Verification

PR #81357 modified two files:

1. src/pages/workspace/expensifyCard/issueNew/ConfirmationStep.tsx - Added Navigation.closeRHPFlow() before navigating to the workspace card page after successful card issuance
2. src/pages/workspace/expensifyCard/issueNew/IssueNewCardConfirmMagicCodePage.tsx - Added Navigation.closeRHPFlow() and changed Navigation.goBack() to use compareParams: false

The files modified directly relate to the Expensify Card issuance flow where the bug occurs. The timing of the merge (Feb 6) aligns with when this would have appeared in staging builds.

Root Cause

The bug is caused by a navigation state conflict introduced in PR #81357. The PR added Navigation.closeRHPFlow() calls to fix a different issue (#80352 - preventing duplicate pages when swiping right after card issuance). However, this introduced a new problem:

When Navigation.closeRHPFlow() is called, it pops the RHP (Right Hand Panel) navigator stack. The closeRHPFlow() function checks if there are multiple routes in the RHP stack and pops accordingly. When this happens during active step transitions in the card issuance flow (e.g., from LimitTypeStep → CardNameStep), the navigation state becomes temporarily inconsistent.

The sequence appears to be:

1. User enters limit amount in LimitTypeStep and taps Next
2. setIssueNewCardStepAndData() updates Onyx with the next step (CARD_NAME)
3. The step component re-renders based on the Onyx state change
4. During the render/navigation transition, if there are any side effects that trigger the closeRHPFlow() logic (potentially from the ConfirmationStep useEffect watching for success states), it causes the previous step to briefly flash before the correct next step renders

This is a classic React Navigation state synchronization issue where closing/popping the navigator while state is updating causes intermediate renders of previous screens.