[$125] Home - After deleting expense, app opens Inbox instead of staying on Home

[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.3.27-0
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: #83019
Email or phone of affected tester (no customers): osidnjodjosijsoji@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Go to Home.
5. Click Begin button on Submit 1 report row.
6. Click More > Delete > Delete.

Expected Result:

App will stay on Home.

Actual Result:

App opens Inbox after deleting expense on Home.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7090167_1772206231834.3.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mukhrr

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022027411209117472604
• Upwork Job ID: 2027411209117472604
• Last Price Increase: 2026-03-02

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

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