You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Merchant field is displayed instead of Distance & Rate field after splitting distance with user #82126
Version Number: 9.3.17-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:#81014 Email or phone of affected tester (no customers):sjoidnjsidjnosnjisjio@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:
Go to staging.new.expensify.com
Go to 1:1 DM with any user.
Click + > Split expense > Distance.
Split a distance expense with the user.
Open the distance expense.
Expected Result:
Distance and Rate field will be displayed.
Actual Result:
Merchant field is displayed instead of Distance & Rate field after splitting distance with user.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #81014 - "fix: Map is missing green line when splitting distance expense, confirm page is empty" by @nkdengineer (High confidence) Related Issues: #80714
Recommendation: REVERT
PR #81014 fixed one issue (missing green line on map for split distance expenses) but introduced a regression in the display logic. The PR modified useFetchRoute to fetch routes for split distance expenses but did not update the corresponding display logic in MoneyRequestView.tsx.
Labels: No label changes needed - keeping DeployBlockerCash as this is a frontend bug in the App repository.
📋 Detailed Analysis
Evidence
PR #81014 modified /home/runner/_work/App/App/src/hooks/useFetchRoute.ts to add:
This change correctly identifies split distance expenses and fetches their routes. However, the display logic in /home/runner/_work/App/App/src/components/ReportActionItem/MoneyRequestView.tsx at line 892 was not updated accordingly.
Verification
The MoneyRequestView component decides whether to show distance fields (Distance & Rate) or merchant field based on this condition at line 892:
isMapDistanceRequest(transaction) returns true (because it has hasDistanceCustomUnit)
BUT transaction?.comment?.waypoints is undefined/empty initially for split expenses
Therefore (isMapDistanceRequest && transaction?.comment?.waypoints) evaluates to false
All other conditions (isManualDistanceRequest, isGPSDistanceRequest, isOdometerDistanceRequest) also return false
So the component falls through to displaying the merchant field instead of distance fields
Root Cause
The PR fixed the route fetching logic by using isDistanceTypeRequest(transaction) which returns true for any transaction with hasDistanceCustomUnit, but the display logic still requires transaction?.comment?.waypoints to be present for map distance requests. This creates an inconsistency where:
Route fetching works correctly (fetches route for split distance expenses)
Display logic fails (shows merchant field instead of distance/rate fields)
The fix should either:
Update MoneyRequestView.tsx line 892 to use similar logic as useFetchRoute (add || isDistanceTypeRequest(transaction))
Or update the condition to check for isDistanceRequest more broadly without requiring waypoints
@jponikarchuk I think the merchant field needs to be there for the distance expense. Rate and distance fields are shown in the split details page. Can you plz test and confirm again
@laurenreidexpensify - as I, @twisterdotcom am already assigned to this issue as BZ, could you also check this box to confirm the Payment Summary above. Note that no single individual can both confirm the payment amounts and approve the payment itself due to SOX.
Activity
melvin-bot commentedon Feb 11, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #81014
melvin-bot commentedon Feb 11, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 11, 2026
Triggered auto assignment to @twisterdotcom (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.github-actions commentedon Feb 11, 2026
👋 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:
OSBotify commentedon Feb 11, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #81014 - "fix: Map is missing green line when splitting distance expense, confirm page is empty" by @nkdengineer (High confidence)
Related Issues: #80714
Recommendation: REVERT
PR #81014 fixed one issue (missing green line on map for split distance expenses) but introduced a regression in the display logic. The PR modified
useFetchRouteto fetch routes for split distance expenses but did not update the corresponding display logic in MoneyRequestView.tsx.Labels: No label changes needed - keeping
DeployBlockerCashas this is a frontend bug in the App repository.📋 Detailed Analysis
Evidence
PR #81014 modified
/home/runner/_work/App/App/src/hooks/useFetchRoute.tsto add:This change correctly identifies split distance expenses and fetches their routes. However, the display logic in
/home/runner/_work/App/App/src/components/ReportActionItem/MoneyRequestView.tsxat line 892 was not updated accordingly.Verification
The MoneyRequestView component decides whether to show distance fields (Distance & Rate) or merchant field based on this condition at line 892:
For split distance expenses:
isMapDistanceRequest(transaction)returnstrue(because it hashasDistanceCustomUnit)transaction?.comment?.waypointsis undefined/empty initially for split expenses(isMapDistanceRequest && transaction?.comment?.waypoints)evaluates tofalseRoot Cause
The PR fixed the route fetching logic by using
isDistanceTypeRequest(transaction)which returns true for any transaction withhasDistanceCustomUnit, but the display logic still requirestransaction?.comment?.waypointsto be present for map distance requests. This creates an inconsistency where:The fix should either:
|| isDistanceTypeRequest(transaction))isDistanceRequestmore broadly without requiring waypointsPujan92 commentedon Feb 11, 2026
@jponikarchuk I think the merchant field needs to be there for the distance expense. Rate and distance fields are shown in the split details page. Can you plz test and confirm again16 remaining items
melvin-bot commentedon Feb 19, 2026
@robertjchen Whoops! This issue is 2 days overdue. Let's get this updated quick!
robertjchen commentedon Feb 20, 2026
Do we still require fixes here? 🤔
twisterdotcom commentedon Feb 20, 2026
I think this is non reproducible, we can close.
nkdengineer commentedon Feb 23, 2026
@twisterdotcom I think me and @Pujan92 should be paid here for the fix since it's not our regression based on this comment, #82126 (comment)
twisterdotcom commentedon Feb 24, 2026
Weird, I wonder why we never assigned you to this issue.
twisterdotcom commentedon Feb 24, 2026
Payment Summary:
twisterdotcom commentedon Feb 26, 2026
@Pujan92 has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-1dbc-a0c6-b532-34d1217d2b34twisterdotcom commentedon Feb 26, 2026
When you have a moment here please @laurenreidexpensify.