Hybrid-After taping the Chat the composer is focused but the keyboard doesn't open

[IuliiaHerets]

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: v9.1.20-2
Reproducible in staging?: Yes
Reproducible in production?: No
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: https://github.com/Expensify/Mobile-Expensify/pull/13494
Issue reported by: Applause Internal Team
Device used: Pixel 7 Pro /Android 15
App Component: Other

Action Performed:

1. Go to staging.expensify.com on the web
2. Choose the 10+ sign-up qualifer > create the account (this should not set the tryNewDot NVP at all and take you into OldDot).
3. Validate the account
4. Switch to HybridApp > Sign in
5. Click the Concierge chat bubble

Expected Result:

The composer to message with the concierge should be visible and focused, and the keyboard should be open and they don't overlap together

Actual Result:

The composer is focused, but the keyboard doesn't open up

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6785523_1743170199001.PR_overlap.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dukenv0307

[melvin-bot]

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

[dangrous]

Seems like this was likely caused by https://github.com/Expensify/Mobile-Expensify/pull/13494 but I'm attempting to confirm locally