[Due for payment 2026-02-23] [GPS mileage expenses] Unit is shown incorrectly in Distance and Rate fields after switching the workspace

[lanitochka17]

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.9-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80604 step 8
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 15 iOS 26.2
App Component: Money Requests

Action Performed:

Preconditions: log in with a new expensifail account.
Create Workspace 1 (default), currency USD, distance unit - miles, rates: default $0.725, new rate $1
Create Workspace 2, currency EUR, unit - kilometers, default rate - €0.725, new rate €3

1. Tap FAB > Track Distance > GPS tab
2. Track some distance, tap Stop - Stop GPS tracking - Next
3. Verify that the default expense policy is used for distance unit in Distance and Rate (miles)
4. Tap Rate, select $1/mile rate, then switch back to default rate
5. Tap "To" field and select Workspace 2
6. Observe the Distance and Rate fields - it displays miles instead of kilometers
7. Tap Rates and observe the Default rate - it is shown as €0.725/mile instead of kilometer

Expected Result:

The Distance and Rate fields show the correct unit after changing the participant workspace

Actual Result:

Unit is shown incorrectly in Distance and Rate fields after switching the workspace

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7059568_1769543005477.CP_1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @greg-schroeder

[melvin-bot]

Triggered auto assignment to @greg-schroeder (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.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh (External)

[M00rish]

Proposal

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

When switching the “To” workspace for a GPS distance request, the Distance and Rate fields keep showing the old unit (e.g., miles) even though the new workspace uses a different unit (e.g., kilometers).

What is the root cause of that problem?

On workspace change we only update customUnitRateID and leave comment.customUnit.distanceUnit untouched:

Participant change sets only the rate ID:

App/src/pages/iou/request/step/IOURequestStepParticipants.tsx

Lines 252 to 264 in 57b2f8c

	if (!isMovingTransactionFromTrackExpense) {
	// If not moving the transaction from track expense, select the default rate automatically.
	// Otherwise, keep the original p2p rate and let the user manually change it to the one they want from the workspace.
	const rateID = DistanceRequestUtils.getCustomUnitRateID({reportID: firstParticipantReportID, isPolicyExpenseChat, policy, lastSelectedDistanceRates});
	if (transactions.length > 0) {
	for (const transaction of transactions) {
	setCustomUnitRateID(transaction.transactionID, rateID);
	}
	} else {
	// Fallback to using initialTransactionID directly
	setCustomUnitRateID(initialTransactionID, rateID);
	}

setCustomUnitRateID does not update distanceUnit:

App/src/libs/actions/IOU/index.ts

Lines 1378 to 1387 in 57b2f8c

	function setCustomUnitRateID(transactionID: string, customUnitRateID: string | undefined) {
	const isFakeP2PRate = customUnitRateID === CONST.CUSTOM_UNITS.FAKE_P2P_ID;
	Onyx.merge(`${ONYXKEYS.COLLECTION.TRANSACTION_DRAFT}${transactionID}`, {
	comment: {
	customUnit: {
	customUnitRateID,
	...(!isFakeP2PRate && {defaultP2PRate: null}),
	},
	},
	});

getRate() prefers the transaction’s stored distanceUnit, so the UI keeps showing the old unit:

App/src/libs/DistanceRequestUtils.ts

Lines 369 to 397 in 57b2f8c

	function getRate({
	transaction,
	policy,
	policyDraft,
	useTransactionDistanceUnit = true,
	}: {
	transaction: OnyxEntry<Transaction>;
	policy: OnyxEntry<Policy>;
	policyDraft?: OnyxEntry<Policy>;
	useTransactionDistanceUnit?: boolean;
	}): MileageRate {
	let mileageRates = getMileageRates(policy, true, transaction?.comment?.customUnit?.customUnitRateID);
	if (isEmptyObject(mileageRates) && policyDraft) {
	mileageRates = getMileageRates(policyDraft, true, transaction?.comment?.customUnit?.customUnitRateID);
	}
	// This will be fixed as part of https://github.com/Expensify/App/issues/66397
	// eslint-disable-next-line @typescript-eslint/no-deprecated
	const policyCurrency = policy?.outputCurrency ?? getPersonalPolicy()?.outputCurrency ?? CONST.CURRENCY.USD;
	const defaultMileageRate = getDefaultMileageRate(policy);
	const customUnitRateID = getRateID(transaction);
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	const customMileageRate = (customUnitRateID && mileageRates?.[customUnitRateID]) || defaultMileageRate;
	const mileageRate = isCustomUnitRateIDForP2P(transaction) ? getRateForP2P(policyCurrency, transaction) : customMileageRate;
	const unit = getDistanceUnit(useTransactionDistanceUnit ? transaction : undefined, mileageRate);
	return {
	...mileageRate,
	unit,
	currency: mileageRate?.currency ?? policyCurrency,
	};

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

When the workspace changes for a distance request, use the setter that updates both rate and unit:

setMoneyRequestDistanceRate already updates distanceUnit (and converts distance if needed):

replace setCustomUnitRateID with setMoneyRequestDistanceRate (passing the policy) for distance requests.

What alternative solutions did you explore? (Optional)

Change getRate() to ignore transaction.comment.customUnit.distanceUnit when the policy changes, but that risks altering existing transactions and doesn’t update stored quantity.

[GCyganek]

Part of GPS feature that I'm responsible for as a Software Mansion engineer, will take care of this

[hoangzinh]

@greg-schroeder, can you help to assign @GCyganek to this issue?

[GCyganek]

Was finishing other GPS stuff, will take care of this tomorrow