[HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$250] Composer focus is lost if a new message is received while typing

[isagoico]

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: v1.4.81-1
Reproducible in staging?: Yes
Reproducible in production?: NO

Issue reported by: @mountiny
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1718015667516489

Action Performed:

Tip: To easily test this, log in with 2 accounts in different devices (e.g: Web & iOS)

1. As account A start typing something in the compose box
2. As account B, sent a message to A while they're typing

Expected Result:

Compose box focus should remain while receiving a new message.

Actual Result:

Compose box focus is lost if the user is typing and a new message is received.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

lost.focus.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b0384bb7db3c3ab2
• Upwork Job ID: 1800145000444915700
• Last Price Increase: 2024-06-10

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

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

[melvin-bot]

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

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

[mountiny]

I dont think this is a backend bug