Expense - After splitting expense, app returns to Reports instead of expense report

[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.3-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: #77657
Email or phone of affected tester (no customers): sjnodijsodijsoijsio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Search

Action Performed:

1. Launch Expensify app.
2. Go to workspace chat.
3. Create two expenses.
4. Go to Reports > Reports.
5. Open the expense report.
6. Open any expense.
7. Tap More > Split.
8. Tap Save.

Expected Result:

After splitting expense, app will return to expense report.

Actual Result:

After splitting expense, app returns to Reports.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @WojtekBoman

[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: #77657 - "Super wide RHP" by @collectioneur (High confidence)
Related Issues: N/A

Recommendation: REVERT

This PR introduced incorrect navigation logic for mobile users when splitting expenses from the Reports flow. The fix is non-trivial and reverting is the safest option to unblock the deploy.

Labels: Keeping DeployBlockerCash (frontend bug, blocks App deploy). Label DeployBlocker was not present on this issue.

Detailed Analysis

Evidence

PR #77657 modified the expense report display architecture to use Super Wide RHP. As part of this change, the navigation logic after splitting expenses was modified in /home/runner/work/App/App/src/libs/actions/IOU/index.ts at line 13888.

The problematic change:

// BEFORE (line 13888):
Navigation.dismissModal();

// AFTER (line 13888):  
Navigation.dismissToSuperWideRHP();

This change occurs in updateSplitTransactionsFromSplitExpensesFlow() when:

• isSearchPageTopmostFullScreenRoute is true, OR
• !transactionReport?.parentReportID is true

Verification

The files affected by this bug:

• /home/runner/work/App/App/src/libs/actions/IOU/index.ts (the navigation logic after split)
• /home/runner/work/App/App/src/libs/Navigation/Navigation.ts (the dismissToSuperWideRHP() method)

Confirmed that PR #77657 modifies these files and introduces the new dismissToSuperWideRHP() method which behaves differently on mobile vs web.

Root Cause

The issue occurs on mobile (narrow layout) when:

1. User navigates: Reports > Reports page > Expense Report > Expense > More > Split
2. User saves the split
3. The code calls dismissToSuperWideRHP()
4. On mobile, dismissToSuperWideRHP() calls dismissModal() which dismisses the ENTIRE modal stack
5. This takes the user back to "Reports" list instead of the expense report

Why this happens:
The dismissToSuperWideRHP() method (line 824-832 in Navigation.ts) has this logic:

function dismissToSuperWideRHP() {
    // On narrow layouts (mobile), Super Wide RHP does not exist, so just dismiss the modal completely
    if (getIsNarrowLayout()) {
        dismissModal();  // <-- This dismisses everything!
        return;
    }
    // On wide layouts, dismiss back to the Super Wide RHP modal stack
    navigateBackToLastSuperWideRHPScreen();
}

The correct behavior should be to use dismissModalWithReport() to navigate back to the expense report, not dismiss everything. The condition at line 13926 likely needs refinement to properly handle the Reports flow vs Search flow.

[francoisl]

cc @mountiny @ZhenjaHorbach

[francoisl]

Demoting as non-critical issue