[Due for payment 2026-06-19] [Due for payment 2026-06-18] [$250] Expense - Error when splitting distance expense in 1:1 DM

[applause-bot]

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

Action Performed:

1. Go to staging.new.expensify.com
2. Open 1:1 DM with any user.
3. Click + > Split expense > Distance.
4. Enter waypoints > Next.
5. Click Split.

Expected Result:

Distance expense will be split in 1:1 DM without issue.

Actual Result:

Error shows up after splitting distance expense in 1:1 DM.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7177430_1781135556679.9.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7177430

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022065098537702017702
• Upwork Job ID: 2065098537702017702
• Last Price Increase: 2026-06-11

Issue Owner

Current Issue Owner: @mallenexpensify

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/7ac97aa2ca8c6e140d2e9aa5eaff0e93e173630cc1319e3faab40f066d1c8fec

[melvin-bot]

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

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

[MelvinBot]

Issue Analysis

⚠️ Medium confidence. Strong leading suspect identified, but one gap remains unexplained (see "Open question"). I couldn't view the Applause video to confirm the exact on-screen error, so please verify before merging a fix.

Leading suspect: PR #92052 migrated SPLIT_BILL_DETAILS from a static route that carried reportID in the path (r/:reportID/split/:reportActionID) to a dynamic-suffix route that drops it (split/:reportActionID). The split-details page now relies on inheriting reportID from the active route instead of reading it from its own path segment — a more fragile resolution that can land you on a not-found / "Failed to parse the path" state when the split preview is tapped.

Why this PR: It's the only change to the split-details flow in this deploy, it's the regression reference on the issue, and "reproducible in staging, not production" matches a freshly-merged routing change (production still uses the old r/:reportID/split/:reportActionID route).

Recommended action (deploy blocker): Revert the SPLIT_BILL_DETAILS portion of #92052 (the room-members migration in the same PR is a separate flow and can stay). A forward-fix would be to re-add reportID to the path (split/:reportID/:reportActionID) and pass it at the two call sites, restoring the old guarantee that reportID is always in the URL.

Mechanism & evidence

• Navigation to split details now builds the URL by appending split/<actionID> to the current active route via createDynamicRoute (createDynamicRoute.ts:64-72), called from MoneyRequestAction.tsx:89 and ChatTransactionPreview.tsx:59.
• The page resolves the report via withReportAndReportActionOrNotFound, which reads route.params.reportID (withReportAndReportActionOrNotFound.tsx:41). Since the new path no longer contains :reportID, this value must be inherited from the parent REPORT screen's params during path parsing — if that inheritance fails, reportID is undefined and the page renders FullPageNotFoundView (DynamicSplitBillDetailsPage.tsx:106).
• The split preview's onPreviewPressed is the trigger; nothing auto-navigates to split details after pressing "Split", so the error surfaces when the freshly-created split preview is tapped (which matches the PR's own QA step "Tap the split preview in chat").

Open question — distance-specificity not fully explained

The PR's QA steps tested a regular amount split in a 1:1 DM and reported it working. The split-details page renders identically for distance and regular splits (the distance branch only flips isMapDistanceRequest/scanning UI — DynamicSplitBillDetailsPage.tsx:79-127). So if the route fully broke reportID resolution, a regular split would fail too — which contradicts the PR QA. That leaves two possibilities I could not disambiguate without the video:

1. Navigation timing/param-resolution edge case that only manifests for the distance flow (e.g. the screen the user lands on after a distance split differs from a regular split, so createDynamicRoute appends to a route not in the SPLIT_BILL_DETAILS entryScreens list).
2. A separate distance-specific error unrelated to 83856 migrate room v2 #92052 — e.g. a backend rejection on the distance split itself surfacing as a red error indicator on the transaction, not a navigation error.

To verify: reproduce on staging, tap the distance split preview, and capture (a) a screenshot of the exact error and (b) the JS console output. A "Failed to parse the path to a navigation state" or a not-found page confirms the routing hypothesis → revert. A red error dot on the transaction with a backend message points to possibility #2 → not this PR.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/93238) to create a draft PR.
To refine: @MelvinBot <your feedback> (e.g. paste the console error / screenshot from staging).
To reject: Explain why you are rejecting Melvin's proposal.

[mjasikowski]

Caused by #84791