[$125] Rerun - Wallet - Card display name does not appear when opened for the first time after import

[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.11-17
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: #80648
Email or phone of affected tester (no customers): Expensifail account
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Android 13 / Xiaomi Poco F5, iOS 15.8.3 / iPhone 7 Plus
App Component: User Settings

Action Performed:

1. Log into NewDot using Expensifail account
2. Go to Wallet > Import transactions
3. Provide a card name and tap Next button
4. Choose this transactions file:
   fake_transactions-2026-01-16 10_56_55.629.csv (attached)
5. Tap the Import button > Got it
6. Tap the recently added card

Expected Result:

The card display name should appear immediately when opened for the first time after import

Actual Result:

The card display name does not appear when opened for the first time after import
Note:

• The card display name will appear after going to another section, then back to open the card in Wallet

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

Bug7062594_1769839861190!fake_transactions-2026-01-16.10_56_55.629.csv

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022018387608605559685
• Upwork Job ID: 2018387608605559685
• Last Price Increase: 2026-02-02

Issue Owner

Current Issue Owner: @thesahindia

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (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 @youssef-lr (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: #80648 - "Release 3.1 - Creating a new Personal Card Feed" by @Gonals (High confidence)
Related Issues: None

Recommendation: REVERT

The PR introduced a new CSV card import feature but has a critical bug where the card display name does not appear when the card is first opened after import. The issue is reproducible on staging only (this is a new feature not yet in production).

Labels: Keeping DeployBlockerCash label (App deploy is blocked). This is a Frontend bug requiring changes to the App repository.

Detailed Analysis

Evidence

PR #80648 was specifically called out by melvin-bot as the recently merged PR, and the bug report states this is for a new feature that "does not exist in prod," matching exactly what PR #80648 introduced - the ability to import transactions from CSV files to create personal card feeds.

The reproduction steps match the new feature:

1. Go to Wallet > Import transactions
2. Provide card name and import CSV file
3. Click the recently added card
4. Card display name does not appear on first open

Verification

The PR modifies several key files related to this functionality:

• src/libs/actions/ImportTransactions.ts - New file that handles the CSV import logic
• src/pages/settings/Wallet/TransactionsImportedPage.tsx - New page for the import flow
• src/pages/settings/Wallet/WalletPage/index.tsx - Modified to integrate the import feature
• src/pages/settings/Wallet/PaymentMethodList.tsx - Modified to display imported cards
• src/ONYXKEYS.ts - Added new Onyx keys for import transaction forms

PR #80648 was merged on 2026-01-30 at 18:56:04Z, which aligns with when this bug would have appeared on staging.

Root Cause

Looking at the ImportTransactions.ts file (lines 287-299), when creating a new card, the PR adds optimistic data that creates the card in CARD_LIST:

if (!isAddingToExistingCard && optimisticCard) {
    const optimisticCardList: CardList = {
        [cardID]: optimisticCard,
    };
    optimisticData.push({
        onyxMethod: Onyx.METHOD.MERGE,
        key: ONYXKEYS.CARD_LIST,
        value: optimisticCardList,
    });
}

However, there is no successData array in the API call (line 352-355). This means that when the API response comes back from the backend, Onyx is not updated with the server-confirmed card data. The optimistic card data is created locally, but when the user navigates away and returns to the card, the app tries to fetch the card data from Onyx, which may not have been properly populated with the nameValuePairs.cardTitle field from the server response.

The issue is that:

1. On initial creation, the optimistic card data is shown (which includes the card name)
2. When navigating away and back, the app re-renders and may be using incomplete data from Onyx that lacks the proper card title
3. The missing successData means the backend response data is never merged into Onyx to replace/update the optimistic data

The fix would require adding proper successData handling to merge the backend response into CARD_LIST with the correct card details including nameValuePairs.cardTitle.