[$250] Android/IOS - Chat - After sent the message the composed box is not focused and cursor is not appear.

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Launch the app
2. Log in with any account
3. Select any user
4. Send message

Expected Result:

After sent the message the composed box is focused and cursor is appeared

Actual Result:

After sent the message - composed box is not focused and cursor is not appear.

Workaround:

Unknown

Platform:

Where is this issue occurring?

• iOS
• Android

Version Number: 1.2.17.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5781260_Screen_Recording_20221017-173830_New_Expensify.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @arosiclair (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[arosiclair]

Can't run iOS current, but repro'd in Android v1.2.16-5. Marking External

[melvin-bot]

Triggered auto assignment to @adelekennedy (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

[melvin-bot]

Triggered auto assignment to @neil-marcellini (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[aimane-chnaif]

The root cause is same as #11867, #11859, #11915

slack convo: https://expensify.slack.com/archives/C01GTK53T8Q/p1665991322162069
pending PR: #11944

According to https://expensify.slack.com/archives/C01GTK53T8Q/p1666028543576899?thread_ts=1665991322.162069&cid=C01GTK53T8Q, #11867 is a master tracking issue

I think it would be good to add all of these issues to 1 tracking issue. And hope this issue would be fixed asap since QA engineers and contributors keep reporting this kind of bug.
cc: @mountiny

[parasharrajat]

We can close this one then if duplicate.

[mountiny]

Closing this out as a duplicate, thank you for the message @aimane-chnaif I have commented in the relevant PR to hopefully speed it up #11944