[$175] Threads -Composer isn't focused after empty the message navigate to another report and return

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: v9.5.1-9
Reproducible in staging?: Yes
Reproducible in production?: Yes
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/76795563/folder/13177078/41237914/1820739544?sort=%2Bidentifier
Email or phone of affected tester (no customers): leungbratt6@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Pixel 7 Pro/Android 17
App Component: Chat Report View

Action Performed:

1. Open the Hybrid app
2. Navigate to any chat and send a message
3. Press the Edit button in the newly added message
4. Empty the draft message input
5. Navigate to a different report
6. Return to the first report
7. Verify that the composer is focused and edit mode is dismissed

Expected Result:

Verify that the composer is focused and edit mode is dismissed

Actual Result:

The composer is not focused

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7276806_1791081283557.focus.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7276806

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022107104987405035552
• Upwork Job ID: 2107104987405035552
• Last Price Increase: 2026-10-05

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/f8512b09554b9f94556affe6f4aa72a78cb4bc87b9f635de0ee334d736049f30

[MelvinBot]

Proposal

TL;DR: On native, this looks like intended behavior, not a regression. Native apps only auto-focus the composer on return when it has text, so the keyboard doesn't pop up. Here the composer is empty, so it isn't focused. I recommend updating the test case's expected result instead of changing code.

What is the root cause of that problem?

1. Opening another report clears all edit drafts in useClearReportActionDraftsOnReportChange.ts:7-13. This ends edit mode, and the composer goes back to the normal draft. That draft is empty because the message was already sent.
2. When the report is shown again, focus requires shouldAutoFocus (ComposerWithSuggestions.tsx:366) or willBlurTextInputOnTapOutside (ComposerWithSuggestions.tsx:922-927). On native, both are false unless the composer has text, because canFocusInputOnScreenFocus/index.native.ts returns false. The code comment at line 923 says native skips this on purpose.
3. The "edit ended" focus call in useEditComposerToggle.ts:97-100 runs while the first report is hidden. That screen's input was just blurred at ComposerWithSuggestions.tsx:893-895, so the focus call has no effect when you return.

Emptying the draft doesn't matter. The result should be the same on native if you leave text in the edit input.

What changes do you think we should make in order to solve the problem?

Update the test case's expected result: "Edit mode is dismissed. The composer is focused on web and desktop, but not on native." This matches fix:67029: allow focus composer on mobile when there is a draft message, whose test steps say an empty composer is "not focused on mobile devices".

What alternative solutions did you explore? (Optional)

If product wants focus on native here:

1. In useEditComposerToggle, check whether the screen is focused when editing ends. If it isn't, set a "pending focus" ref instead of calling onFocus.
2. Add that ref to the focus condition at ComposerWithSuggestions.tsx:925, so the composer focuses when the screen is shown again.

This fix only works if the first report stays mounted. If the report remounts, the pending focus would also need to survive the remount.

Investigation details

• On narrow layouts, edits happen in the bottom composer, not inline (ChatMessageContent.tsx:64).
• Allow editing messages in Composer on narrow screens V2 changed edits so they are discarded when you leave the report. Before that, under Allow empty draft messages, this test expected the empty edit input to still be there. The expected result was later rewritten to "focused and edit mode dismissed". That holds on web and desktop only.
• I didn't find a PR that changed how native handles focus. I didn't test this on a device, and I couldn't view the Applause video.
• Related: Android - Compose box - Draft message input reappears after clearing and navigating uses the same steps on Android.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/103036) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

---

view run

[melvin-bot]

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

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022107104987405035552