Search - Keyboard overlaps the conversation opened from search results/start chat

[lanitochka17]

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.0.16-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): gatantm+81@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch new Expensify
2. Tap on Fab > Start Chat or Search
3. Search for a user
4. Tap on the user

Expected Result:

User is navigated to the new chat with focus on the text field which is shown correctly

Actual Result:

User is navigated to the new chat but the keyboard is overlapping the text field and send button and can't sent any message

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

Add any screenshot/video evidence

Bug6560330_1722616325557.RPReplay_Final1722615383.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[lanitochka17]

We think that this bug might be related to #vip-vsp

[kirillzyusko]

I can work on that issue on Monday (but if it's urgent to solve then someone else can have a look) 👀

Potentially (though not sure absolutely) this issue can be introduced by these changes: #46513

[Beamanator]

If a revert PR can quickly fix the 2 open blockers, let's go for it (other blocker: #46745)

[Beamanator]

Quick fixed by reverting in #46749

[Beamanator]

Confirmed fixed in staging!