Wallet - Assigned cards section is shown when there is no card

[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.11-53
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79562
Email or phone of affected tester (no customers): ffjfujggngngjghjg@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.2
App Component: User Settings

Action Performed:

Precondition:

• Account does not have any card.

1. Launch Expensify app.
2. Go to Account > Wallet.

Expected Result:

Assigned cards section will not show up if there is no card.

Actual Result:

Assigned cards section is shown when there is no card.

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]

You have been assigned to this deploy blocker because you recently merged this PR: #79562

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

Triggered auto assignment to @heyjennahay (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]

👋 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: #79562 - "Feat: existing personal cards" by @waterim (High confidence)
Related Issues: None

Recommendation: REVERT

The PR should be reverted because it introduces a visible UI bug where the "Assigned cards" section header and description are shown even when there are no cards to display.

Labels: No label changes needed - this is correctly labeled as DeployBlockerCash since it is a frontend bug that requires an App PR fix.

Detailed Analysis

Evidence

The issue reports that the "Assigned cards" section is shown in the Wallet page even when there are no cards. This is reproducible on staging but not in production, and PR #79562 was merged on 2026-01-30 and is included in the current staging deploy.

PR #79562 introduced personal cards to the Wallet page and made changes to:

1. The isPersonalCard() function logic (inverted the logic to correctly identify personal cards)
2. Added the hasDisplayableAssignedCards() function to check if cards should be displayed
3. Modified the WalletPage to show personal cards in the assigned cards section

Verification

The bug is in /home/runner/work/App/App/src/pages/settings/Wallet/WalletPage/index.tsx:

Lines 547-575 show the issue:

<Section
    subtitle={translate('walletPage.assignedCardsDescription')}
    title={translate('walletPage.assignedCards')}
    isCentralPane
    subtitleMuted
    titleStyles={styles.accountSettingsSectionTitle}
>
    {hasAssignedCard && (
        <PaymentMethodList
            shouldShowAddBankAccount={false}
            shouldShowAssignedCards
            onPress={assignedCardPressed}
            ...
        />
    )}
    {isBetaEnabled(CONST.BETAS.PERSONAL_CARD_IMPORT) && (
        <View>
            <MenuItem ... />
        </View>
    )}
</Section>

The Section header and subtitle are always rendered, but the PaymentMethodList inside is only shown when hasAssignedCard is true. This means when hasAssignedCard is false, users see the section header/description with no content underneath.

Root Cause

The PR correctly modified the logic but failed to wrap the entire Section component with a conditional check. The Section should only be displayed when either:

1. hasAssignedCard is true, OR
2. The personal card import beta is enabled

The fix would be to wrap the entire Section with a conditional like:

{(hasAssignedCard || isBetaEnabled(CONST.BETAS.PERSONAL_CARD_IMPORT)) && (
    <Section ...>
        ...
    </Section>
)}

However, since this is a deploy blocker, the safest approach is to revert the PR and re-implement with proper testing.