[HOLD for payment 2024-11-29] [$250] Search - The shortcut CTRL + K does not work with a user as employee in a WS

[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.0.59-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5191872
Issue reported by: Applause - Internal Team

Action Performed:

1. Sign in to the app with a new Gmail account
2. Choose "Get paid back by my employer" from the onboarding tasks
3. Type a Name and Last name and click the "Continue" button
4. Go to Settings, create a new workspace and invite a new account as an employee
5. Log in with the new employee's account in incognito mode
6. Press the shortcut CTRL + K to open search dialog

Expected Result:

The shortcut CTRL + K to open the search dialog should open correctly

Actual Result:

Pressing the combination CTRL + K to open the search dialog does not execute, while the other shortcuts such as CTRL + J and CTRL + D work correctly

Workaround:

Unknown

Platforms:

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

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6658921_1731075276789.Ctrl___k_doesn_t_Work.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021854902169710515284
• Upwork Job ID: 1854902169710515284
• Last Price Increase: 2024-11-13
• Automatic offers:
• dukenv0307 | Contributor | 104806147
• truph01 | Contributor | 104867213

Issue Owner

Current Issue Owner: @abekkala

[melvin-bot]

Triggered auto assignment to @danieldoglas (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[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.

[mountiny]

I ran into this problem in production already cc @daledah I believe someone pointed to your PR here #51547 any chance you could have a look?