[Guided Setup Stage 2] Keyboard not opened when navigating to enter name screen

[izarutskaya]

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: 1.4.64-1
Reproducible in staging?: Y
Reproducible in production?: N
Found when validating PR : #39951
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Open the app and log in with a new account
2. Tap Settings > Troubleshoot > Onboarding Flow
3. Select any option

Expected Result:

The keyboard is opened, and placeholder is pushed up

Actual Result:

The keyboard is not opened until the field is selected, and cursor is overlapping the placeholder

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

Bug6457804_1713811214247.video_2024-04-22_14-39-27.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

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

[izarutskaya]

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.

[izarutskaya]

We think this issue might be related to the #vip-vsb.

[mountiny]

@filip-solecki @rezkiy37 @cdOut could you please fix this in your onboarding PRs? thanks!

[rezkiy37]

I am fixing this problem in my PR.

[rezkiy37]

Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue.

[rezkiy37]

I've tried to reproduce the bug. I was not able to get it. It works properly on an emulator and a real Android device.

Details

Android.1.mp4

Android.2.mp4

Android.3.mp4

[joekaufmanexpensify]

I also cannot reproduce.

2024-04-23_15-59-56.mp4

[joekaufmanexpensify]

Is anyone able to consistently reproduce this?

[mountiny]

@kavimuru @izarutskaya can you please check what device/ android version have you reproed this at?

[joekaufmanexpensify]

I'm going to close this for now since it cannot be reproduced. Happy to take another look if someone ends up being able to consistently reproduce this on a specific device/android version.