Ecard - Activate physical card is not displayed and there is no error on the Address page

[lanitochka17]

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.99-0
Reproducible in staging?: Y
Reproducible in production?: Unable to check in Prod because of this KI
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #56305
Email or phone of affected tester (no customers): applausetester+ag1702@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition: Use an Expensifail account as an employee of a collect workspace with E-Card enabled.
The employee has been assigned a physical card and the personal details are not filled.

1. Navigate to https://staging.new.expensify.com/
2. Go to Wallet
3. Click on the physical card
4. Click on Get physical card
5. Enter name and DoB > Next
6. On address page, manually fill in the address instead of selecting an address from the suggestion dropdown
7. Enter phone number > Next
8. Click on Confirm
9. Enter magic code
10. Verify that the Get physical card button is still displayed
11. Click on Get physical card

Expected Result:

The Activate physical card button is displayed after completing the "Get physical card" flow

Actual Result:

The Activate physical card button is not displayed after completing the "Get physical card" flow. When trying to complete the flow again, there is no error on the Address page and the State/ Province field has been cleared

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6745795_1739803786399.56305-Web.1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @iwiznia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

@daledah @DylanDylann can you check this one please?

[francoisl]

It looks like with #56305 we no longer use RequestPhysicalExpensifyCard and instead rely entirely on SetPersonalDetailsAndShipExpensifyCards, did that require additional backend changes that aren't live yet maybe?

[francoisl]

FWIW this might have happened because that command blocks shipping cards if the domain uses the test Plaid account - see internal logs.

Error processing command 'ShipExpensifyCard' (403 Card is on testing feed), ignoring.

@mountiny it looks like you worked on this command, do you know if we need to update test steps in general for e Expensify Card moving forward? In the meantime, should we demote this, or revert #56305?

[iwiznia]

Ah thanks @francoisl! Indeed that's the error. I think updating the steps to test that PR is the way to go, no?
Also, this is not a blocker then.

[mountiny]

@francoisl Correct, we updated the command to ensure physical cards tied to the plaid testing account are not shipped. I will reach out to QA to update the test steps 👍