Expensify Card - No error message when incorrect code is entered when deactivating card

[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.60-0
Reproducible in staging?: Y
**Reproducible in production?:**N, New feature
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: N/A
Email or phone of affected tester (no customers): applausetester+zm27@applause.expensifail.com
Issue reported by: Applause - Internal Team
Slack conversation (hyperlinked to channel name):

Issue found when executing PR #51147

Action Performed:

Precondition:

• User has a virtual card

1. Go to staging.new.expensify.com
2. Go to Wallet
3. Click on the virtual card
4. Click Report virtual card fraud
5. Click Deactivate card
6. Enter incorrect magic code

Expected Result:

There will be error for incorrect magic code

Actual Result:

There is no error for incorrect magic code.
App shows not here page briefly and then empty card details page loads

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

Bug6661758_1731354317140.20241112_034102.mp4

View all open jobs on GitHub

[melvin-bot]

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

[lanitochka17]

New feature, not repro on Production

bandicam.2024-11-11.15-55-42-076.mp4

[francoisl]

This will require backend changes, reassigning and demoting.

[melvin-bot]

@francoisl, @youssef-lr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[francoisl]

I think the last piece was https://github.com/Expensify/Auth/pull/12739 and we can close this now, right @youssef-lr?

[youssef-lr]

Yup!