[Hold on #15992] Composer not focused when user leaves/returns an ongoing DM draft

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. go to any chat
2. click on composer
3. click on users name to see the details
4. close the details page

Expected Result:

composer should focused (same as web, mWeb)

Actual Result:

composer not focused

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.91-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

az_recorder_20230329_150759.1.mp4

Screen_Recording_20230329_164112_Chrome.mp4

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680088305065359

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @michaelhaxhiu (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[MelvinBot]

@michaelhaxhiu Huh... This is 4 days overdue. Who can take care of this?

[michaelhaxhiu]

@bondydaa do you think we should close this GH or keep it on hold for #15992?

[michaelhaxhiu]

Posted in slack here - https://expensify.slack.com/archives/C049HHMV9SM/p1680715074199869?thread_ts=1680301816.029279&cid=C049HHMV9SM

[michaelhaxhiu]

Holding till we hear back. This is valid but it may be better to consolidate with the tracking GH.

[bondydaa]

I think the SOP has been to put a HOLD on any issues created and link it on the tracking GH.

[michaelhaxhiu]

Excellent, let's do the same here. Thanks Bondy :)

This job is on hold for #15992