[$250] Android - Spend - User is navigated out of report after adding an existing expense.

[jponikarchuk]

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.65-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: #85225
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Search

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the Expensify app.
2. Open any workspace chat.
3. Create a manual expense.
4. Create an empty report.
5. Navigate to "Spend" > "Reports"
6. Open the empty report created on step 4.
7. Tap on "Add Expense" > "Add existing expense"
8. Select the expense created on step 3 and add it to report.
9. Note that after expense is added, user is navigated out of report, landing on "Reports" section again.

Expected Result:

User should remain on report after adding an existing expense to it.

Actual Result:

User is navigated out of report after adding an existing expense to it while on "Reports" section on "Spend".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022050258929939771054
• Upwork Job ID: 2050258929939771054
• Last Price Increase: 2026-05-01

[melvin-bot]

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

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #85225 - "Feat: Change Add unreported expense to Add existing expense in a report" by @nyomanjyotisa (High confidence)
Related Issues: #84130 (the feature request this PR implements)

Recommendation: REVERT

PR #85225 introduced this regression and can be cleanly reverted. The bug is staging-only (new feature, not in production), and the navigation issue is contained within this PR's scope.

Assigned: @nyomanjyotisa (PR author), @sobitneupane, @puneetlath (approving reviewers)
Labels: DeployBlockerCash kept — this is a Frontend bug in Expensify/App. No label changes required; the existing label is correct.

Detailed Analysis

Evidence

• The melvin-bot and the issue body both directly link PR Feat: Change Add unreported expense to Add existing expense in a report #85225 as the causing PR.
• PR Feat: Change Add unreported expense to Add existing expense in a report #85225 was merged on 2026-04-29 and is listed in the StagingDeployCash for version 9.3.65-0, matching the version in the bug report.
• The bug is reproducible on staging but not production ("new feature, doesn't exist in prod"), consistent with a regression introduced by this staging-only PR.
• The affected flow ("Add Expense > Add existing expense") is exactly what PR Feat: Change Add unreported expense to Add existing expense in a report #85225 introduced (renamed from "Add unreported expense" and expanded to include Draft expenses).

Verification

• Affected file: src/pages/AddExistingExpense.tsx — this file was substantially modified by PR Feat: Change Add unreported expense to Add existing expense in a report #85225 (146 additions, 34 deletions).
• Affected component: src/components/AddExistingExpenseFooter.tsx — renamed from AddUnreportedExpenseFooter and updated in PR Feat: Change Add unreported expense to Add existing expense in a report #85225.
• The PR modifies the screen name, route, navigator, and linking config for this flow, confirming it owns the navigation behavior in question.

Root Cause

When the user is on "Spend > Reports" and opens a report, then invokes "Add Expense > Add existing expense", the modal is opened as a RHP. On narrow layout (Android HybridApp), AddExistingExpenseFooter.handleConfirm calls Navigation.dismissToSuperWideRHP(), which on narrow layouts resolves to dismissModal(). This dismisses the entire RHP modal stack, navigating the user back to the previous fullscreen route — which is "Reports" — rather than keeping them on the report they were viewing.

The underlying dismissToSuperWideRHP call was present in the prior AddUnreportedExpenseFooter as well, but the specific scenario that reproduces the bug (opening the flow from a report in "Spend > Reports" then adding a Draft expense) is new behavior enabled by this PR. The PR expanded the eligible transactions to include expenses on open expense reports (Draft status), creating a new user path that surfaces this dismiss-navigates-away behavior in the "Spend > Reports" context.