Profile - User receives a magic code instead of the secondary login verification

[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.28-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4912495
Email or phone of affected tester (no customers): fischer9966+090224aa@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com or open Expensify App
2. Login with Gmail account
3. Go to Settings > Profile > Contact Method
4. Tap to "New Contact Method"
5. Enter new email for secondary login

Expected Result:

User receives email with verification code for the secondary login

Actual Result:

User receives a magic code for primary login instead of verification code for the secondary login

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6592115_1725390798272.Web-Secondary-Login-get-MC-instead-of-verify-code.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

@lanitochka17 This is now the new expected behaviour as described in this PR #48320

To add a secondary login, the user now has to first validate they have access to the primary login by adding that magic code first. Only then, if successful, they can validate the secondary login.

Can you please update the testrail accordingly?

[isagoico]

TC - https://expensify.testrail.io/index.php?/cases/view/2593732 - Has been updated to reflect this behavior.

[mountiny]

Thanks!