[PAYMENT MAY 16] [$250] Merge account - App proceeds to next step when phone number has invalid format

[nlemma]

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.1.24-2
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+sdsoidsj@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: User Settings

Action Performed:

1. Launch Expensify app.
2. Go to Settings > Security.
3. Tap Merge account.
4. Enter a phone number with two letters (+18005555555ab)
5. Mark "I understand this is not reversible" checkbox.
6. Click Next.

Expected Result:

App will not allow to proceed to the next page because the phone number has invalid format (+18005555555ab).

Actual Result:

App allows to proceed to the next page when the phone number has invalid format (+18005555555ab).
If the phone number with three letters is entered (+18005555555abc), the field will throw error.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6796020_1744117675093.20250408_210710.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021909635743785763886
• Upwork Job ID: 1909635743785763886
• Last Price Increase: 2025-04-08
• Automatic offers:
• daledah | Contributor | 106918832

Issue Owner

Current Issue Owner: @

[melvin-bot]

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

[nlemma]

@abekkala FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[MarioExpensify]

From this comment, it looks like we'll be putting Merge behind a beta and thus all deploy blockers will be demoted.

Regarding the issue itself, we can handle this Externally. I tested locally and it seems the awesome-phonenumber package we use here does not handle this case effectively, allowing up to 2 characters being added before flagging the phone as invalid.

This lib is used throughout the App and we may already have problems happening elsewhere.