Reports - Keyboard is opened and closed when navigating to "Chats" section.

[mitarachim]

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: 9.1.51-0
Reproducible in staging?: Yes
Reproducible in production?: No
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): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome
App Component: Other

Action Performed:

1. Open the staging.new.expensify.com website.
2. Navigate to "Reports"
3. Tap on the bookmark icon and select "Chats"
4. Note that keyboard is opened and closed, and that navigation bar is moved up and down too.

Expected Result:

Keyboard should remain closed when navigating to "Chats" section on "Reports"

Actual Result:

Keyboard is opened and closed when navigating from "Expenses" to "Chats" on "Reports" section. Also, navigation bar is moved up and down.

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

Bug6840562_1748029896164.Up.mp4

View all open jobs on GitHub

[melvin-bot]

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

[ikevin127]

I don't think any recent PR caused this, and since autoFocus is set to false in SearchPageHeaderInput, this seems really difficult to debug because even if we try to log Keyboard events, nothing is logged even though the keyboard does appear to show briefly. Additionally, none of the input onFocus functions seem to be triggered.

If this is not caused by us, it might be a chromium issue 🤔

Note: This is not a deploy blocker, just a minor UI/UX issue which does not prevent the user from using the app in any way.

[jliexpensify]

This is not a deploy blocker, just a minor UI/UX issue which does not prevent the user from using the app in any way.

Agreed, I think e can demote this @JS00001

[JS00001]

We are going to revert anyways, so we will probably end up closing this

[Beamanator]

adding back priority label just so you don't lose track of this

[JS00001]

this was reverted, so closing for now