[Due for payment 2026-07-08] Expensify Card - Card frozen message is shown in multiple lines and overlaps with next cell

[applause-bot]

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

Action Performed:

Precondition:

• Workspace has at least one virtual Expensify Card.
• User invites another member as admin to the workspace.
• The invited member has email as display name.
• The invited member freezes a virtual card.
• Perform the steps below as the owner:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Expensify Card.

Expected Result:

Card frozen message will be shown in one line and will not overlap with next cell.

Actual Result:

Card frozen message is shown in multiple lines and overlaps with next cell.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7192418

Issue Owner

Current Issue Owner: @luacmartins

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/cd9df9f19190124fda01df6efda33475295d7b792eb5233c5b9c17b43ec5d295

[melvin-bot]

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

[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.

[mountiny]

I am not sure how it should look like even with the new styles. Since regression testing is done and we getting through the last blockers, I think revert is the best option, though I am sorry to do that since its the only blocker from the PR.

@Expensify/design in the meantime, can you help provide mocks for how to handle this situation so the frozen card information is useful and visible in this design?