[Due for payment 2026-07-03] Android & iOS - Distance - Map in GPS does not use the new compass icon as Map tab

[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.17-0
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: #93026
Email or phone of affected tester (no customers): sdjnoisdjdosijsonssjo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 15 Pro Max / iOS 26.5
App Component: Money Requests

Action Performed:

1. Launch Expensify app.
2. Open FAB > Track distance > Map.
3. Go to GPS.

Expected Result:

Map in GPS will use the same new compass icon as Map tab.

Actual Result:

Map in GPS does not use the new compass icon as Map tab.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7188100_1782172335799.ScreenRecording_06-23-2026_07-50-11_1.mp4

View all open jobs on GitHub

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

[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/a19413b0a3ff8eeee7fef178f45691295976a5bd7a1d3e22ddfe6ecd047c1d2a

[melvin-bot]

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

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

Proposal

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

The GPS map (FAB > Track distance > Map > GPS) still shows Mapbox's default native compass instead of the new custom compass icon that PR #93026 introduced for the regular Map tab.

What is the root cause of that problem?

PR #93026 ("Use custom compass on the maps") swapped the native Mapbox compass for a custom Compass SVG overlay — but only in MapView.tsx, not in the separate native GPSMapView.tsx that backs the GPS distance flow.

In MapView.tsx the native compass is turned off and the custom SVG is rendered as an overlay:

• MapView.tsx:286 — compassEnabled={false}
• MapView.tsx:355-372 — custom expensifyIcons.Compass overlay (with bearing-tracking animated style + tap-to-reset-north).

GPSMapView.tsx was left untouched and still relies on the native compass:

• GPSMapView.tsx:210-211 — compassEnabled + compassPosition.

So the two map surfaces render two different compasses, which is exactly the reported symptom.

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

Port the custom-compass treatment from MapView.tsx into GPSMapView.tsx:

1. Set compassEnabled={false} on the Mapbox.MapView and remove compassPosition (GPSMapView.tsx:210-211).
2. Render the custom expensifyIcons.Compass SVG as an absolutely-positioned overlay, mirroring MapView.tsx:355-372, including the bearing-driven compassAnimatedStyle and the resetMapToNorth press handler so behavior matches the Map tab.

Notes & alternatives considered

• The cleanest long-term fix is to extract the compass overlay into a shared component so the two map implementations can't drift again, but for a deploy-blocker the minimal port above is lower-risk.
• This is entirely within the Expensify/App repo (frontend), so it can be fixed here directly.
• Confidence: High — code paths confirmed; the symptom (old compass only in GPS) matches a file the PR did not touch.

---

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

[GCyganek]

Will take care of this, the PR that adds custom GPS map was merged first and then the one with the custom compass, I'll add the custom one on the GPS map in a moment