[Due for payment 2025-08-15] [$250] Expensify card - "Expensify Card was not found" on limit page after opening invalid card page

[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.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://test-management.browserstack.com/projects/2148171/test-runs/TR-137/folder/12015321/39317910/797468434?sort=%2Bidentifier
Email or phone of affected tester (no customers): applausetester+210701kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace is set up with Expensify card feature.
• Admin has assigned a virtual card to themselves.

1. Go to staging.expensify.com
2. Go to workspace settings > Expensify Card.
3. Open the virtual card that is assigned to yourself.
4. Copy the card details link.
5. Click Deactivate card > Deactivate.
6. Navigate to the copied card details link from Step 4.
7. Close the RHP.
8. Click Issue card.
9. Select user, choose card type and limit type.
10. Proceed to limit input page.

Expected Result:

There will be no error on limit input page.

Actual Result:

Limit input page shows "The Expensify Card was not found".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021947920264966209953
• Upwork Job ID: 1947920264966209953
• Last Price Increase: 2025-07-23
• Automatic offers:
• thelullabyy | Contributor | 108168096

Issue Owner

Current Issue Owner: @stephanieelliott

[melvin-bot]

Triggered auto assignment to @stephanieelliott (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.

[thelullabyy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On the Limit Input page, the error message "The Expensify Card was not found" is displayed incorrectly when starting a new issue card flow.

What is the root cause of that problem?

The issueNewExpensifyCard data is not cleared when initiating a new issue card flow. If a previously deactivated Expensify Card triggered an error, that stale error state persists in issueNewExpensifyCard, causing the incorrect error message to appear even for valid cards.

App/src/pages/workspace/expensifyCard/issueNew/LimitStep.tsx

Line 84 in 233790a

formID={ONYXKEYS.FORMS.ISSUE_NEW_EXPENSIFY_CARD_FORM}

What changes do you think we should make in order to solve the problem?

In this section, where the new issue card flow begins, we should reset the issueNewExpensifyCard data—either fully or at least its errors field—to ensure that stale errors do not persist between sessions.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

What alternative solutions did you explore? (Optional)

An alternative would be to perform the cleanup (which mentioned in main solution) in the issueNewExpensifyCard action itself, specifically here, ensuring the error state is cleared whenever the action is invoked.

Or in here we can use ${ONYXKEYS.COLLECTION.ISSUE_NEW_EXPENSIFY_CARD}${policyID} instead.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021947920264966209953

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External)

[allroundexperts]

@thelullabyy's proposal looks good to me. The RCA is clear and the proposed solution works as well.

🎀 👀 🎀 C+ reviewed

[melvin-bot]

Triggered auto assignment to @dangrous, see https://stackoverflow.com/c/expensify/questions/7972 for more details.