[HOLD for payment 2024-12-19] [HOLD for payment 2024-12-17] Profile - Invalid second contact method is added and displayed as ready to verify.

[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.73-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5320066&group_by=cases:section_id&group_order=asc&group_id=229064
Email or phone of affected tester (no customers): ibellicotest+86@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Open the Expensify app.
2. Tap on "Settings" and select "Profile"
3. Open the "Contact Method" tab.
4. Tap on "New Contact Method"
5. Complete with an Email with an existing account.
6. Wait for the magic code to be received and type it.
7. Verify that an error message is displayed, showing that the account can´t be added as contact method.
8. Close the error message and tap on the arrow on the top left corner.
9. Verify that the account wasn´t added as second contact method.

Expected Result:

Invalid Email or Email with existing account, shouldn´t be added as secondary contact method after the error message is closed.

Actual Result:

After the user receives and closes an error message, showing that an account can´t be added as contact method, the account is added anyway and is displayed as ready to verify. The user receives a magic code to verify the account, but all the codes received are rejected.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6689509_1733797910567.Contact.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

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

[melvin-bot]

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

[MonilBhavsar]

Commented on the suspicious PR #53462