[Due for payment 2025-11-06] [$250] Thread - When tap "Reply in thread" the keyboard opens and closes, thread convo opens with delay

[lanitochka17]

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: 9.1.41.0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6045599
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch the iOS Hybrid app and sign in
2. Navigate to any chat and send a message
3. Long press on the message and choose "Reply in thread"

Expected Result:

User is immediately navigated to the thread conversation

Actual Result:

The menu modal is dismissed. The keyboard opens and closes quickly in the main chat (Can be seen when pause the video, screenshot added). Then there is a second delay, and user is navigated to the thread conversation. The issue occurs only when tapping "Reply in thread" for the first time on a particular message

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6824635_1746642211553.Reply_in_thread.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021920771777424990234
• Upwork Job ID: 1920771777424990234
• Last Price Increase: 2025-11-04

Issue Owner

Current Issue Owner: @bfitzexpensify

[melvin-bot]

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

[truph01]

Proposal

Please re-state the problem that we are trying to solve in this issue.

• When tapping "Reply in thread", the keyboard briefly opens and then closes, and the thread conversation opens with a noticeable delay. This results in a jarring and unintuitive user experience.

What is the root cause of that problem?

• The issue stems from the logic found here:
  

  App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx

  Lines 282 to 286 in bd59655

  	hideContextMenu(false, () => {
  	KeyboardUtils.dismiss().then(() => {
  	navigateToAndOpenChildReport(reportAction?.childReportID, reportAction, originalReportID);
  	});
  	});

  
  Specifically, the use of KeyboardUtils.dismiss() causes the app to wait for the keyboard to close before initiating navigation.

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

• We should consider removing the KeyboardUtils.dismiss() call for all platforms except Android, as the original bug appears to only occur on Android.

• Alternatively, we can consider removing KeyboardUtils.dismiss() entirely, assuming the original bug is no longer reproducible across any platform.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

• None.

What alternative solutions did you explore? (Optional)

• Instead of calling KeyboardUtils.dismiss(), we could call ReportActionComposeFocusManager.composerRef?.current?.blur().

[melvin-bot]

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

[melvin-bot]

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

[parasharrajat]

@truph01 Can you link the original bug?

[truph01]

@truph01 Can you link the original bug?

@parasharrajat This one #55136