[Due for payment 2026-05-18] [Due for payment 2026-05-15] Distance - Distance is not split after editing distance during split

[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.68-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: #85493
Email or phone of affected tester (no customers): josdjnosdjionjsdonjisod@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 a distance expense.
4. Open the expense.
5. Click More > Split.
6. Open any split.
7. Click Distance > Manual tab (or Map tab).
8. Edit distance and save it.

Expected Result:

RHP will return to edit split page.

Actual Result:

RHP closes and distance is not split.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7146587_1778108690304.4.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @aimane-chnaif

[melvin-bot]

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

[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: #85493 - "Allowing distance to be edited while editing" by @mukhrr (High confidence)
Related Issues: None

Recommendation: REVERT

PR #85493 introduced a navigateBackAfterSave function that calls Navigation.closeRHPFlow() instead of the original navigateBack() which called Navigation.goBack(backTo). When editing the distance of a split expense, closeRHPFlow() closes the entire RHP stack rather than navigating back to the split edit page, causing the behavior described in this issue.

Assigned: @mukhrr (PR author), @aimane-chnaif and @youssef-lr (approving reviewers) from highest-confidence causing PR only
Labels: DeployBlockerCash KEPT (frontend App PR caused the issue). DeployBlocker should be REMOVED since this is a frontend bug requiring an App fix, not a backend fix.

Detailed Analysis

Evidence

• The issue was filed against version 9.3.68-0, which is the current StagingDeployCash version. PR Allowing distance to be edited while editing #85493 is confirmed listed in that staging checklist and was merged on 2026-05-06.
• The melvin-bot automatically assigned the PR author to this deploy blocker, identifying PR Allowing distance to be edited while editing #85493 as the trigger.
• The issue test name/ID in the bug report directly references https://github.com/Expensify/App/pull/85493, confirming regression testing caught this against that exact PR.

Verification

• The affected code path is src/pages/iou/request/step/IOURequestStepDistance.tsx, src/pages/iou/request/step/DistanceManualTabContent.tsx, and src/pages/iou/request/step/DistanceMapTabContent.tsx — all modified by PR Allowing distance to be edited while editing #85493.
• The PR modifies the distance editing flow and introduces two new components (DistanceManualTabContent, DistanceMapTabContent) that tab between manual distance entry and map-based entry during editing.

Root Cause

PR #85493 added a new navigateBackAfterSave callback that unconditionally calls Navigation.closeRHPFlow(). This is called after saving a distance edit in both the map submit path (submitWaypoints) and the new manual distance submit path (submitManualDistance). The previous behavior used navigateBack() which called Navigation.goBack(backTo) — respecting the backTo param and returning to the correct prior screen (e.g., the split edit page). Navigation.closeRHPFlow() dismisses the entire RHP regardless of the navigation context, so when the user is editing a split's distance, the entire RHP closes instead of returning to the split edit view.

The fix is to revert PR #85493 (or, alternatively, to restore Navigation.goBack(backTo) in the navigateBackAfterSave callback — but a clean revert is safer given the size and complexity of the change).