[Bug]: Waypoint 'separatesLegs' flag not being applied during navigation

[RL-William-Coates]

Mapbox Navigation SDK version

3.3.1

Steps to reproduce

Create a multi-waypoint route with the map matching API, set 'separatesLegs' to false for all waypoints except the first and last. Start navigation.

Expected behavior

The voice instructions do not call out waypoints as destinations.

Actual behavior

The voice instructions are calling out waypoints as destinations.

As demonstrated by the screenshots below. Waypoint 2 is at the end of the road, and the voice instructions are calling it out as a destination. If I print out the step instructions of the route, waypoints are not being treated as destinations.

Is this a one-time issue or a repeatable issue?

repeatable

[kried]

Hi @RL-William-Coates

We were unable to reproduce your problem. Both voice and visual instructions do not mention silent waypoints, also the problem does not repeat itself during reroutes.

Could you please share the history route file with us so we can investigate your specific route? You can record it using HistoryRecorder. There is a sample app using historyRecorder.

Or you can send us a sample app or code sample where you can reproduce the issue.

[RL-William-Coates]

Hi @kried

Attached is a history replay of me reproducing the issue.

Also attached is a modified version of History-Recording.swift to help you reproduce the issue yourself. The main changes are in the userDidLongTap logic, and requestRoute() function. Simulate Navigation must be OFF. Here are some further instructions:

Set initial user location: 51.994726, -2.394331

Create first waypoint at: 51.998013, -2.379042
Create second waypoint at: 52.036780, -2.422791

Start navigation

Change user location to: 51.994930, -2.394601 (this needs to cause a rerouting event)
Change user location to: 51.994985, -2.393452 (this helps you get back on route)

Now both the voice and visual instructions treat the middle waypoint at the end of Beach lane as a destination. It even displays a waypoint marker on the map.

history_replay.gz
History-Recording.swift.zip

[kried]

Thank you for the detailed report. We were able to reproduce the problem and pass it on to the corresponding Directions API team.