Sign in-Unable to sign in with validated account after signing out, validation loop

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.25-3
Reproducible in staging?: Yes
Reproducible in production?: No
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.4 Chrome, iPhone 15 iOS 18.3.2
App Component: Other

Action Performed:

1. Sign out of the staging.new.expensify.com
2. Enter email of the validated account in the input field on the Sign in page
3. Click Continue

Expected Result:

Magic code input is displayed

Actual Result:

"Validate" green button is displayed with the text "We've been unable to deliver SMS messages to [email protected], so we've suspended it temporarily. Please try validating your number:". After clicking Validate there is a message "Your number has been validated! Click below to send a new magic sign-in code" and "Send" button. After clicking Send the first "Validate" message is displayed again.
The same issue occurring in OD.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6797529_1744230256134!new.txt
https://github.com/user-attachments/assets/c7002421-dd44-4812-a1a9-a489c3096e86

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (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]

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

[blimpich]

Oof. This isn't good. I'm also getting this locally.

[blimpich]

Reverting a suspicious PR, seeing if that fixes it.

[blimpich]

Reverting this PR locally fixed it. Setting up a revert PR.

[ChavdaSachin]

@blimpich I think you should take a look at this PR before reverting any #59956.

[rushatgabhane]

Fixed here - #59956

[blimpich]

Fix was deployed to staging. Checked it, it works fine now. Closing.