[Due for payment 2026-06-10] [$250] Expensify Card - Error shows up when freezing physical card

[mitarachim]

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.34-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #81880
Email or phone of affected tester (no customers): applausetester+khcategory20@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace is set up with Expensify Card.
• Assign yourself a physical card.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Expensify Card.
3. Click on the physical card.
4. Click Freeze card.
5. Click Freeze card.

Expected Result:

Physical card can be frozen.

Actual Result:

Error shows up when freezing physical card.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7098275_1773094701903.6.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022043665197655195386
• Upwork Job ID: 2043665197655195386
• Last Price Increase: 2026-05-18

Issue Owner

Current Issue Owner: @mallenexpensify

[getusha]

@Pujan92 @ShridharGoel is this reproducible?

[MelvinBot]

Proposal

What is the root cause of that problem?

The freeze card feature was introduced in PR #81880. When the user clicks "Freeze card", the app calls freezeCard() in Card.ts:805-861 which issues API.write(WRITE_COMMANDS.FREEZE_CARD, {cardID}). The optimistic update sets the card state to STATE_SUSPENDED (7). When the backend rejects the request, the failure handler at Card.ts:837-851 fires, reverting the state and setting a generic error (common.genericErrorMessage).

The most likely cause is that the backend FreezeCard command handler is either not deployed or returns an error for physical cards. The frontend code itself is logically correct — it's the API call that fails.

There is also a secondary issue: WorkspaceExpensifyCardDetailsPage.tsx has no error rendering UI for card-level errors. The failure handler sets errors on the card Onyx data, but the details page never displays them. Errors are only rendered on the card list page (WorkspaceExpensifyCardListPage.tsx:165-170) via OfflineWithFeedback.

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

1. Backend fix (primary): Ensure the FreezeCard command handler is deployed and correctly handles physical card freeze requests. This is most likely a backend deployment or handler issue.

2. Frontend fix (secondary): Add error rendering to WorkspaceExpensifyCardDetailsPage.tsx — wrap the freeze/unfreeze menu items in OfflineWithFeedback and display card.errors so users see feedback when the API call fails, rather than the action silently reverting.

What alternative solutions did you explore?

• Checked whether fundID resolution (card?.fundID ?? defaultFundID ?? CONST.DEFAULT_NUMBER_ID) could produce an incorrect workspaceAccountID, causing wrong Onyx keys. This would be a cosmetic issue (wrong optimistic update target) but would not explain the API error itself.
• Checked whether isCardFrozen() in CardUtils.ts:1435 could have a logic issue — it correctly checks both state === STATE_SUSPENDED and frozen metadata, so this is not the cause.

Related issues

• [$250] Expensify Card - Frozen card cannot be replaced, but RHP shows success page #84776 — Frozen card cannot be replaced (likely related to the same freeze feature rollout)

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

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

[melvin-bot]

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