Login - There is No phone number is +15005550006 at the error when typed 2 digits and continue

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue found when executing PR #8511

Action Performed:

1. Go to staging.new.expensify.com
2. Type 2 digits and continue
3. Verify that the phone number is +15005550006 at the error

Expected Result:

There is phone number is +15005550006 at the error when typed 2 digits and continue

Actual Result:

There is No phone number is +15005550006 at the error when typed 2 digits and continue

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.88.1

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): none

Logs: https://stackoverflow.com/c/expensify/questions/4856

Recording.896.mp4

Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[johnmlee101]

@kbecciv the video evidence for this is for a different issue? I cannot reproduce otherwise

[kbecciv]

@johnmlee101 Sorry about that, updated correct video.

Recording.896.mp4

[johnmlee101]

Okay to clarify the issue is that the error message doesn't pop up for invalid numbers, not that "No phone number is +15005550006"

[johnmlee101]

I think this is caused by cd40818 cc @yuwenmemon

[yuwenmemon]

Okay looked into this for a bit, but a lot has changed (and is changing) with regards to error handling and Onyx so I'm just going to revert that previous PR to get the error handling right

[yuwenmemon]

Reverted the offending PR