mapbox / mapbox/mapbox-navigation-ios
[Bug]: Route line is missing while in navigation
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 918
- Forks
- 326
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Mapbox Navigation SDK version
Mapbox navigation 2.18.4
Steps to reproduce
We are using .gpx file to simulate user location update from 22 Bellios Lane to 9 Boon Keng Rd
- We start trip first time and simulate user location to destination using .gpx file
- When user reach to the destination we stop navigation
- After that we reset user location using the same .gpx file
- When we start the second trip to the same destination again, using same .gpx file, at this time the route line is missing in navigation
I have a question:
- Is there any caching data from Mapbox sdk that recorded user already reached to destination . And after that if user start the same trip to the same destination Mapbox will immediately updated user is on arrive destination ?
- If we have caching data like that, how can we clean it up to start the second trip normally ?
Expected behavior
When we start the second trip at step 4 the route line should be shown normally while app is in navigation
Actual behavior
Route line is missing in second trip navigate to the same location
Is this a one-time issue or a repeatable issue?
repeatable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the second-trip case in Mapbox Navigation SDK 2.18.4 using the same GPX route from 22 Bellios Lane to 9 Boon Keng Rd. Check whether restarting navigation after reaching the destination leaves the route line missing, and determine whether the second trip displays the route normally without retained arrival state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100