[HOLD for payment 2024-10-14] [HOLD for payment 2024-10-11] [$250] Distance - Waypoints change to duplicate waypoints after drag and drop waypoints

[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.0.44-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5040727
Email or phone of affected tester (no customers): applausetester+pso@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to FAB > Submit expense > Distance
3. Enter three waypoints A - B - C
4. Drag waypoint B to waypoint C and now it becomes A - C - B
5. Drag waypoint C to waypoint B

Expected Result:

The resulting waypoints will be A - B - C

Actual Result:

The resulting waypoints become A - C - C

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6623484_1727976649706.20241004_012620.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021841915588250417056
• Upwork Job ID: 1841915588250417056
• Last Price Increase: 2024-10-03
• Automatic offers:
• nkdengineer | Contributor | 104254910

Issue Owner

Current Issue Owner: @mananjadhav

[melvin-bot]

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

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

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021841915588250417056

[melvin-bot]

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

[Beamanator]

This looks external b/c I'm seeing that the data sent to the backend (for GetRouteForDraft looks like it's incorrect / in the incorrect order), so it looooks like it's the front end's fault for sending the wrong data