[Due for payment 2025-11-17] [Due for payment 2025-09-26] [Due for payment 2025-09-16] Expense - Nothing happens after pressing Enter on Delete confirm modal

[mitarachim]

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.2.1-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #68190
Email or phone of affected tester (no customers): sdjionjsoijdso@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.expensify.com
2. Go to workspace chat.
3. Submit an expense to the workspace chat.
4. Click on the expense preview.
5. Click More > Delete.
6. Press Enter to delete it (do not click on the confirm modal).

Expected Result:

The expense will be deleted.

Actual Result:

Nothing happens after pressing Enter on Delete confirm modal.
The chat in the background is focused instead.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6933809_1756857247715.Screen_Recording_2025-09-03_at_07.51.54.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

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

[mollfpr]

@zirgulis @alitoshmatov Could you create a quick fix for this?