[Due for payment 2025-07-04] [$250] Onboarding - Unable to tap Verify button when keyboard is opened during onboarding

[mitarachim]

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.55-1
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: #62489
Email or phone of affected tester (no customers): lfffffdjdjdjdkdkd@agiuse.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.5
App Component: Other

Action Performed:

1. Launch Expensify app.
2. Log in with this private domain email - @agiuse.com
3. Enter name > Next.
4. Tap on the magic code input field.
5. With keyboard opened, tap Verify.

Expected Result:

Error message will show up.

Actual Result:

Keyboard closes.
Error message only shows up after tapping Verify for the second time.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6849098_1748899789263.ScreenRecording_06-03-2025_05-26-34_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021930693641506849935
• Upwork Job ID: 1930693641506849935
• Last Price Increase: 2025-06-05

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

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

[twisterdotcom]

How is this flow followed? I can't get from step 2 where I create an email on a private domain to step 3 where I am asked for a name without validating anyway.

New Account Android App	Existing account Android App
screen-20250603-101439.mp4	screen-20250603-101635.mp4

Perhaps this needs a non-verified domain?