Hybrid - Android - Room - Keyboard is not opened when creating a new room

[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: 9.0.67-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5267320&group_by=cases:section_id&group_order=asc&group_id=229067
Email or phone of affected tester (no customers): ibellicotest+43@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Open the Expensify app.
2. Tap on the FAB and select "Start Chat"
3. Tap on "Room"
4. Add a name for the room and tap on "Create Room"
5. Verify you land on the new created room and the keyboard is opened.

Expected Result:

After creating a new room and landing on chat, the keyboard should be opened.

Actual Result:

Keyboard is not opened after creating a new room and landing on chat.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6677650_1732678571997.Create_Room.mp4

View all open jobs on GitHub

[melvin-bot]

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

[mjasikowski]

trying to reproduce locally

[mountiny]

Discussing in the slack thread https://expensify.slack.com/archives/C01GTK53T8Q/p1732693067945429, I think we can demote this one and keep looking into it as not a blocker