iOS - Distance - Unable to move waypoint freely in landscape mode

[nlemma]

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.54-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: #85229
Email or phone of affected tester (no customers): jsdjosidjiojisojio3@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.3
App Component: Money Requests

Action Performed:

1. Launch Expensify app in landscape mode.
2. Go to workspace chat.
3. Tap + > Track distance > Map.
4. Enter 5 waypoints.
5. Rotate the device landscape.
6. Scroll down to the 5th waypoint.
7. Long tap on the 5th waypoint and try to move it up to the 1st waypoint.

Expected Result:

User can freely move waypoint without issue.

Actual Result:

User can only move the waypoint within the viewport. User cannot move 5th waypoint up to the 1st waypoint.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7124354_1775617299983.ScreenRecording_04-08-2026_10-59-17_1.MP4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @GCyganek

[melvin-bot]

@mjasikowski recently merged #85229, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @luacmartins (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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