[Due for payment 2026-04-17] [Personal Card Import] Add personal card - "Something not working?" modal appears briefly, then disappears

[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.50-2
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: #84042 step 6
Email or phone of affected tester (no customers): applausetester+ii_27031@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 15 iOS 26.3.1
App Component: Other

Action Performed:

1. Sign in to ND with a new expensifail account
2. Navigate to the Account tab, open Wallet page
3. Tap Add personal card
4. Select a country other, than US (Poland, for example), then tap Next
5. On the Plaid modal tap "x" button in the top right corner, then "Yes, exit"

Expected Result:

"Something not working?" modal appears with "Report issue" and "Skip" buttons

Actual Result:

"Something not working?" modal appears briefly, then it disappears, and the keyboard opens

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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: #84042 - "Add personal card steps" by @narefyev91 (High confidence)
Related Issues: None found

Recommendation: REVERT

PR #84042 introduced a race condition in the Plaid exit flow that causes the "Something not working?" modal to appear briefly then immediately disappear due to concurrent navigation.

Labels: No changes made. DeployBlockerCash should remain as this is a Frontend bug caused by an App PR.

Detailed Analysis

Evidence

• The issue description directly links to PR Add personal card steps #84042 step 6 as the test case that reproduces the bug
• PR Add personal card steps #84042 was merged on 2026-03-26 at 18:33:09Z and is included in the current staging deploy (9.3.50-2)
• The bug is reproducible only on staging, where PR Add personal card steps #84042 exists, and N/A for production (new feature does not exist)
• The bug occurs specifically in the "Add personal card" flow introduced by this PR

Verification

The bug occurs in these files from PR #84042:

• /home/runner/_work/App/App/src/pages/settings/Wallet/PersonalCards/AddNewCardPage.tsx - Manages the modal state
• /home/runner/_work/App/App/src/pages/settings/Wallet/PersonalCards/steps/PlaidConnectionStep.tsx - Handles Plaid exit

Confirmed: PR #84042 added both files and they are central to the reported bug.

Root Cause

When the user exits the Plaid modal by tapping the X button:

1. PlaidConnectionStep.tsx line 176-179 calls handlePlaidLinkExit():

const handlePlaidLinkExit = () => {
    onExit?.();              // Sets modal visible = true
    handleBackButtonPress(); // Navigates back immediately
};

2. AddNewCardPage.tsx line 64 passes onExit={() => setIsModalVisible(true)}:

case CONST.PERSONAL_CARDS.STEP.PLAID_CONNECTION:
    CurrentStep = <PlaidConnectionStep onExit={() => setIsModalVisible(true)} />;

3. The modal is set to visible (line 74-86 in AddNewCardPage.tsx), but handleBackButtonPress() executes immediately after, navigating away and unmounting the component before the modal can render.

This creates a race condition where:

• Modal visibility is set to true
• Navigation occurs on the same tick
• Component unmounts before modal can display
• User sees a brief flash as described in the bug report

The fix requires waiting for user interaction with the modal before navigating, or moving the navigation logic to the modal confirmation handlers.