First character of search input often missing when typing quickly after Cmd+K

[m-natarajan]

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
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
Expensify/Expensify Issue URL:
Issue reported by: @tgolen
Slack conversation (hyperlinked to channel name): #Quality

Action Performed:

1. Navigate to inbox
2. Press Cmd+K to open the chat search modal
3. Immediately start typing a search term
4. Observe that the first character is often missing from the input field

Expected Result:

The search input should be ready to capture keystrokes as soon as the modal appears, even if the user types quickly.

Actual Result:

The first keystroke is sometimes ignored if typing begins immediately after opening the modal.

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

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Krishna2323

[melvin-bot]

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

[mountiny]

Putting this on hold. It seems like a direct consequece of this change #65855 @allgandalf @Krishna2323 @amyevans

I dont think we can add a timemout there, the original bug was probably less bad than this

[amyevans]

Hmm yeah, #65855 morphed from its initial fix that only applied to native apps (where I think users aren't going to be able to start typing quickly in the same way as you can with a hardware keyboard), to applying on all platforms with a CP'ed PR: #68198.

the original bug was probably less bad than this

Agreed

[mountiny]

@Krishna2323 @allgandalf can you please look into fixing this, I agree that this does not make much sense on web

[Krishna2323]

@mountiny, the PR only added a delay on native platforms. I don't think this is related to #65855. Please correct me if I misunderstood something.

[mountiny]

@Krishna2323 this PR adds the delay to web too #68198 doesn't it?

[melvin-bot]

@lschurr Whoops! This issue is 2 days overdue. Let's get this updated quick!

[Krishna2323]

Thanks for explaining! I was looking at the original PR. I will raise the follow-up by EOD tomorrow.

[Krishna2323]

@mountiny Could you please assign this to me so I don’t forget to raise the PR?