Home - Prompt box is not focused after closing CMD+SHIFT+K or CMD+J RHP for the second time

[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: 9.4.61-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98336
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Other

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Home.
3. Type anything on Concierge prompt box.
4. Press CMD+SHIFT+K or CMD+J.
5. Click RHP back button.
   → Prompt box is focused.
6. Press CMD+SHIFT+K or CMD+J.
7. Click RHP back button.

Expected Result:

Prompt box will be focused after closing CMD+SHIFT+K or CMD+J RHP.

Actual Result:

Prompt box is not focused after closing CMD+SHIFT+K or CMD+J RHP for the second time.

This issue is not reproducible with CMD+K (search router).

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7243255_1787748910247.8.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7243255

[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/b10e066cc68e3f7ad3b5e67858702160d6539a96fb872001da8d232a3035a0eb

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #98336

[melvin-bot]

@puneetlath @ZhenjaHorbach you have been assigned to this deploy blocker because you reviewed the offending PR: #98336

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

@adamgrzybowski you have been assigned to this deploy blocker because you authored the offending PR: #98336

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source