Chat - Composer is not focused after returning from Reports to Inbox or switching between chat

[jponikarchuk]

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.2.87-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-2490/folder/13176681/41237002/1089921203?q=focus&issue_type=jira Email or phone of affected tester (no customers): [email protected] Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Chat Report View

Action Performed:

Bug 1:

1. Go to staging.new.expensify.com
2. Go to any chat.
3. Focus on the composer.
4. Go to Reports.
5. Go back to Inbox.

Bug 2:

1. Go to staging.new.expensify.com
2. Go to any chat.
3. Focus on the composer.
4. Go to different chat.

Expected Result:

Composer will be focused.

Actual Result:

Composer is not focused after returning from Reports to Inbox or after switching between chat.

Workaround:

Unknown

Platforms:

• [ ] Android: App
• [ ] Android: mWeb Chrome
• [ ] iOS: App
• [ ] iOS: mWeb Safari
• [ ] iOS: mWeb Chrome
• [x] Windows: Chrome
• [x] MacOS: Chrome / Safari

Screenshots/Videos

https://github.com/user-attachments/assets/b6ce4c13-40c7-40e5-bab1-efd3ddba491f

https://github.com/user-attachments/assets/dc50af36-d8d7-465f-92b7-2dcff28c289c

View all open jobs on GitHub

[melvin-bot[bot]]

Everybody was OOO, so I assigned 10 random eligible people.

[melvin-bot[bot]]

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

[github-actions[bot]]

:wave: 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.

[melvin-bot[bot]]

💬 A slack conversation has been started in #expensify-open-source

[aimane-chnaif]

@jponikarchuk can you please retest in 9.2.87-3? Not able to reproduce

[jasperhuangg]

This was most likely fixed by the react navigation upgrade revert.

https://github.com/Expensify/App/pull/78443

I reverted it for https://github.com/Expensify/App/issues/78435 where there were also focus issues happening.

[jasperhuangg]

https://expensify.enterprise.slack.com/archives/C09V78U42D8/p1766698667050129 retest requested

[m-natarajan]

Not repro on Mac Chrome build 9.2.87-4

https://github.com/user-attachments/assets/582ed68e-4193-4e7d-9e52-b5d56392b00f

[laurenreidexpensify]

Gonna close as not reproducible