Company cards - Infinite loading on Add cards page when adding direct feed

[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.2.96-1
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory around #78470
Email or phone of affected tester (no customers): kiatest.80+ck18261@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11/Chrome, iPhone 16/iOS 18.7.1
App Component: Workspace Settings

Action Performed:

1. Launch Hybrid app or navigate to staging.new.expensify.com
2. Create Collect workspace
3. Go to workspace settings >> Company cards
4. Click Add cards >> Next >> Direct Feed >> Other >> Go through Plaid flow selecting Regions or Wells Fargo bank
5. Select Last Day of month >> Submit

Expected Result:

User able to add direct feed & No infinite loading appears on Add cards page

Actual Result:

-Infinite loading on Add cards page when adding direct feed

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: #78470

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @garrettmknight (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: #77205 - "Remove BETA_PLAID_COMPANY_CARDS" by @nkuoch (High confidence)
Related Issues: None found

Recommendation: REVERT

PR #77205 introduced a regression in the Plaid company card onboarding flow that causes infinite loading when users try to add a direct feed via Plaid.

📋 Detailed Analysis

Evidence

PR #77205 removed the BETA_PLAID_COMPANY_CARDS beta flag and made Plaid company cards available to all users. While removing the beta checks in most places, the PR inadvertently broke the flow in StatementCloseDateStep.tsx.

Before PR #77205:

const isPlaid = isBetaEnabled(CONST.BETAS.PLAID_COMPANY_CARDS) && !!addNewCard?.data?.publicToken;

After PR #77205:

const isPlaid = !!addNewCard?.data?.publicToken;

Root Cause

When adding a Plaid direct feed, the flow is:

1. User completes Plaid connection
2. User is shown the Statement Close Date selection page (StatementCloseDateStep.tsx)
3. User selects "Last Day of month" and clicks Submit

The bug occurs in step 3. When isPlaid is true, the submit function (line 31-37 in StatementCloseDateStep.tsx) sets the step back to BANK_CONNECTION:

if (isPlaid) {
    setAddNewCompanyCardStepAndData({
        step: CONST.COMPANY_CARDS.STEP.BANK_CONNECTION,
        data: {statementPeriodEnd: statementPeriodEnd ?? null, statementPeriodEndDay: statementPeriodEndDay ?? null},
    });
    return;
}

This causes the BankConnection page to render again. The BankConnection page shows an infinite loading indicator when isPlaid is true (line 208-226 in BankConnection/index.tsx), waiting for the feed to be created. However, the importPlaidAccounts function that actually creates the feed is never called because the navigation flow gets stuck.

Before the PR, when users were NOT in the beta, isPlaid would be false, so the statement close date submission would directly call addNewCompanyCardsFeed to create the feed (line 40-51), avoiding this circular navigation issue.

This issue only reproduces on staging and not production because PR #77205 is only on staging (merged Jan 2, 2026).