[HOLD for payment 2024-11-01] [HOLD for payment 2024-10-30] Profile - "Failed to add this contact method" error appears when correct magic code is entered

[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.52-2
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh081006@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Account settings > Profile > Contact method.
3. Click New contact method.
4. Enter a new contact method > Click Add.
5. Enter incorrect magic code.
6. Click RHP back button without clearing the magic code and the error message.
7. Click Add.
8. Enter incorrect magic code.
9. Clear the field.
10. Enter the correct magic code, then hit Enter (important, do not use cursor to click Verify).
11. Note that the new contact method shows "Failed to add this contact method.".
12. Click on the new contact method.
13. Magic code page opens despite the error message.

Expected Result:

In Step 11, there should not be "Failed to add this contact method." error under the new contact method, because the correct magic code is entered in Step 10, and also magic code page opens in the next step (Step 13) which means there is no issue with adding the contact method.

Actual Result:

In Step 11, there is "Failed to add this contact method." error under the new contact method.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6642214_1729611656948.20241022_232609.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[melvin-bot]

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

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

[rlinoz]

Caused by: #49445

Looks like a fix is almost ready: #51267