[Due for payment 2025-07-17] [$250] Fix replacing physical Expensify Card flow

[joekaufmanexpensify]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: @joekaufmanexpensify
Slack conversation (hyperlinked to channel name): #convert

Action Performed:

Prereq: Have the Expensify Card enabled with a non-test bank account (so you can issue physical Expensify Cards)

1. From account A issue account B a physical card.
2. As account B, order the card.
3. Go the wallet.
4. Click on the card (now pending activation).
5. Go through the flow to mark the card as stolen, which replaces it.

Expected Result:

Three different bugs here:

1. When account B is initially issued the card, there should be a report action in the workspace chat advising them the card was issued, and another one when it was shipped.
2. When account B gets to the magic code step of replacing a card, we should automatically trigger the magic code.
3. When account B successfully replaces the card, we should show some kind of confirmation and land them on the wallet after, immediately showing their new card.

Actual Result:

1. The report action when you're issued physical card and after the card ships is missing in the workspace chat.
2. We didn't automatically trigger the magic code on the last step of the replace card flow. I tested twice and both times I didn't initially receive a magic code. When I requested a new one after 30 seconds, it appeared right away.
3. After replacing the card, I saw an error in the RHP and then landed on the wallet with no card shown and an RBR in the wallet page. Leaving the wallet and coming back then showed the new card which was successfully replaced.

The replace card issues happened both when replacing a card pending activation and with an already active card.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

2025-04-30_18-00-57.mp4

2025-04-30_17-59-04.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021917925085751646864
• Upwork Job ID: 1917925085751646864
• Last Price Increase: 2025-05-01
• Automatic offers:
• dominictb | Reviewer | 107219197

Issue Owner

Current Issue Owner: @joekaufmanexpensify

[melvin-bot]

Current assignee @joekaufmanexpensify is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

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

[melvin-bot]

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