Expensify Card - New card is not shown in profile unless Expensify Card page is visited first

[IuliiaHerets]

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.0.92-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5532547
Email or phone of affected tester (no customers): applausetester+100106kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• User has assigned themselves a virtual card.

1. Go to staging.new.expensify.com
2. Go to Wallet.
3. Click on the card.
4. Click Report virtual card fraud.
5. Click Deactivate card.
6. Enter magic code.
7. Click Got it, thanks.
8. Go to Workspace settings > Members.
9. Click on your profile.
10. Note that the new card which is created after deactivation is missing in profile.
11. Go to Workspace settings > Expensify Card.
12. Go back to Workspace settings > Members.
13. Click on your profile.

Expected Result:

In Step 10, the new card after the previous card is deactivated should appear in member profile page.

Actual Result:

In Step 10, the new card after the previous card is deactivated does not appear in member profile page.
It only appears after Expensify Card page is visited in Step 13.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6728337_1738227189014.20250130_164713.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mountiny

[melvin-bot]

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

[DylanDylann]

@mountiny @koko57 It seems we have a similar bug before

[koko57]

yes, it's being worked on - #55571
I think we can close this one and solve it in the 55571

cc @mountiny

[mountiny]

still on it

[melvin-bot]

@mountiny @Christinadobrzyn this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!