mapbox / mapbox/mapbox-navigation-ios
[Bug]: (Re-)Routing Issue
A pull request for this has already been merged.
- #4186 by @1ec5 — merged
- Dominant language
- Swift
- Stars
- 918
- Forks
- 326
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Mapbox Navigation SDK version
2.7.1
Steps to reproduce
We are recognizing issues with the route progress information and the route state (is on route or not). We are using map matching to create a route by our own GPS coordinates for cycling purposes. When leaving the route and returning to the the route on another point, the route progress information are no longer correct.
In this example repository you can find more information about our problem:
https://github.com/brose-ebike/ios-mapbox-routing-issue
To reproduce it you have to do:
- Checkout the project
- Setup the tokens
- Start the project and use one of the example GPX files attached in the project for simulating the location.
Expected behavior
The routing information (isOnRoute, remainingTime, remainingDistance) should update again correctly when returning to the route.
Actual behavior
The routing information (isOnRoute, remainingTime, remainingDistance) are not updating when leaving the route and coming back to the route without executing a rerouting.
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 with the linked example repository and its GPX files; set up the tokens, run the project, and simulate leaving and rejoining the route. Observe route progress and route state while checking isOnRoute, remainingTime, and remainingDistance. Done means these values update correctly after returning to the route without rerouting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100