Android - Expense - After navigating back from the Workspace Chat, the “Not here” page appears

[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.38-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #84656
Email or phone of affected tester (no customers): biruknew45+78hjs@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: android
App Component: Money Requests

Action Performed:

1. https://staging.new.expensify.com/
2. Go to a workspace chat
3. Create an expense
4. Open it
5. Click More > Split > Save
6. Open any split
7. Click Report > Create report
8. On the remaining expense, click Amount
9. Click on the highlighted row
10. Click Remove split
11. Click Save
12. After it navigates you to WS chat click on Back navigation

Expected Result:

Not here page shouldn't appear, back navigation should navigate to the correct page

Actual Result:

After navigating back from the Workspace Chat, the “Not here” page appears, and navigating back again opens WS chat again, and navigating again opens WS settings page.

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

[melvin-bot]

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

[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: #84656 - "Fix Not Here page after removing split expense" by @MelvinBot (High confidence)
Related Issues: #84612 (the issue #84656 was trying to fix)

Recommendation: ROLL FORWARD

PR #84656 attempted to fix a "Not here" page issue when removing split expenses, and it successfully fixed the initial navigation. However, it introduced a new regression: when users navigate back AFTER being taken to the workspace chat, they encounter a "Not here" page. This suggests that while #84656 correctly navigates to the parent chat report when the expense report is deleted, it does not fully clean up the navigation stack.

The issue is staging-only (not reproducible in production), confirming this is caused by PR #84656 which is only on staging.

A revert would reintroduce the original bug from #84612. Instead, the fix should enhance the navigation stack cleanup in updateSplitTransactionsFromSplitExpensesFlow to remove all intermediate screens that reference the deleted expense report, not just the transaction thread.

Labels: Keeping DeployBlockerCash (App deploy blocked - this is a frontend bug requiring App code changes)

📋 Detailed Analysis

Evidence

The reproduction steps in this issue are nearly identical to the test steps in PR #84656, with one critical addition: step 12 - "click on Back navigation" after being taken to the workspace chat. This extra back navigation triggers the "Not here" page.

PR #84656 test steps end with: "Verify the expense report RHP closes and navigates to the workspace chat without showing Not here page" ✅ This works.

Issue #85408 adds: "After it navigates you to WS chat click on Back navigation" → "Not here page appears" ❌ This fails.

Verification

The affected code is in /home/runner/_work/App/App/src/libs/actions/IOU/Split.ts, specifically the updateSplitTransactionsFromSplitExpensesFlow function (lines 1694-1763).

PR #84656 modified this function to:

1. Call setDeleteTransactionNavigateBackUrl to suppress "Not here" during transition (line 1712)
2. Navigate to parent chat when expense report is deleted (line 1747)
3. Remove the transaction thread screen from navigation stack (line 1761)

However, it only removes the transactionThreadReportScreen and does not clean up other screens in the navigation stack that may reference the now-deleted expense report (such as the split expense detail screens or the expense report detail screen itself).

Root Cause

When updateSplitTransactionsFromSplitExpensesFlow performs a reverse split that deletes the expense report:

1. It correctly navigates to the parent chat (workspace chat) via dismissModalWithReport
2. It removes the transaction thread screen in requestAnimationFrame
3. However, there are still intermediate screens in the navigation stack pointing to the deleted expense report
4. When the user presses back, the navigation tries to go to one of these screens showing the deleted report
5. Since the report is deleted, ReportScreen shows "Not here" page

The fix in PR #84656 was incomplete - it addressed the immediate navigation but did not fully clean up the navigation history.

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On Android, after splitting an expense, creating a report from one split, removing the remaining split (triggering a reverse-split), and saving, the user is navigated to the Workspace Chat. However, pressing the hardware Back button from the WS chat shows a "Not here" page instead of normal back navigation. Further back presses create a loop between the WS chat and the "Not here" page.

This is a regression introduced by #84656, which was supposed to fix the same "Not here" page issue but introduced an incomplete navigation stack cleanup.

What is the root cause of that problem?

The root cause is that updateSplitTransactionsFromSplitExpensesFlow in src/libs/actions/IOU/Split.ts leaves a stale expense report screen in the navigation back stack after a reverse-split deletes the expense report. Here's the sequence:

1. The function correctly calls setDeleteTransactionNavigateBackUrl to temporarily suppress the "Not here" page, and then calls dismissModalWithReport({reportID: parentChatReportID}).

2. On Android (narrow layout), dismissModalWithReport calls navigate(reportRoute, {forceReplace: true}) (src/libs/Navigation/Navigation.ts:773). Since the RHP (split expense page) is the focused root-level route, the REPLACE action operates at the root level -- it replaces the RHP with a new ReportsSplitNavigator containing the WS chat, while the old ReportsSplitNavigator (containing the now-deleted expense report screen) remains in the back stack.

3. The code then only removes the transaction thread report screen via removeScreenByKey (Split.ts:1756-1762), but does not remove the expense report screen from the old SplitNavigator.

4. DeleteTransactionNavigateBackHandler (src/pages/inbox/DeleteTransactionNavigateBackHandler.tsx:18-31) clears the deleteTransactionNavigateBackUrl via a deferred callback when the old expense report screen loses focus.

5. When the user presses Back, the new SplitNavigator (single route, no sidebar on narrow layout) pops entirely, revealing the old SplitNavigator with the stale expense report screen. Since deleteTransactionNavigateBackUrl is already cleared and the report's reportID was set to null by the optimistic deletion, shouldShowNotFoundPage (src/pages/inbox/ReportScreen.tsx:511-554) returns true, showing the "Not here" page.

What changes do you think we should make in order to solve the problem?

In updateSplitTransactionsFromSplitExpensesFlow (src/libs/actions/IOU/Split.ts), when isLastTransactionInReport is true, the expense report screen should also be removed from the navigation stack after dismissModalWithReport completes, alongside the existing transaction thread screen removal.

The approach should follow the pattern used by other deletion flows (e.g., MoneyReportHeader, MoneyRequestHeader): instead of using dismissModalWithReport (which pushes forward and leaves stale entries), first dismiss the RHP, then navigate back past the expense report screen to the parent chat. This ensures the deleted report's screen is naturally removed from the back stack rather than lingering.

Alternatively, after dismissModalWithReport, look up the expense report screen via Navigation.getReportRouteByID(expenseReportID) and explicitly remove it -- though this would require enhancing removeScreenByKey or removeReportScreen to handle screens nested inside SplitNavigators (currently they only filter root-level routes).

What alternative solutions did you explore? (Optional)

• Keeping the deleteTransactionNavigateBackUrl set longer: This would only mask the symptom. The stale screen would still be in the navigation stack, and clearing the URL at any point would expose the "Not here" page again.
• Using Navigation.removeReportScreen(new Set([expenseReportID])) after navigation: This existing utility only operates on root-level routes and would miss nested screens inside SplitNavigators on narrow layout.
• Reverting PR Fix Not Here page after removing split expense #84656: This would re-expose the original issue ([Due for payment 2026-03-24] [$250] Expense - Not here page opens after removing split #84612). The fix is mostly correct -- it just needs the additional step of cleaning up the expense report screen from the navigation stack.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[Valforte]

@abzokhattab can you take a look and see if you can whip up a quick fix for this bug? If so we can CP it.

[abzokhattab]

@MelvinBot implement this