mapbox / mapbox/mapbox-navigation-android
Off Route issue
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Android API:
Mapbox Navigation SDK version:
Mapbox API components used:
implementation 'com.mapbox.navigation:ui-v1:1.1.0-beta.6'
implementation 'com.mapbox.navigation:router-offboard:1.1.0-beta.6'
implementation 'com.mapbox.mapboxsdk:mapbox-android-plugin-annotation-v9:0.8.0'
Observers used:
OffRouteObserver:
Navigation starts off successfully
07Jul20-09:21:34 4000 INFO MyMapboxNavigationActivity$1.onOffRouteStateChanged : 254 => $$$ MAPBOX : ENTER : is offRoute = false
We go off route for some reason and apparently loose communication with Mapbox instructions
07Jul20-09:22:18 4000 INFO MyMapboxNavigationActivity$1.onOffRouteStateChanged : 254 => $$$ MAPBOX : ENTER : is offRoute = true
We go back on route but still have no apparent communication or limited communication with Mapbox instructions.
It also appears that several waypoints have been skipped in the process of coming back on route.
07Jul20-09:22:29 4000 INFO MyMapboxNavigationActivity$1.onOffRouteStateChanged : 254 => $$$ MAPBOX : ENTER : is offRoute = false
Steps to trigger behavior
Please see attached file for more detailed setup/options information
MAPBOX_BUG_SUBMISSION_07JUL20.txt
- request a route with 25 waypoints
- start navigating the route
- the on/off/on route transitions start
Expected behavior
transition from on route to off route and back to on route should maintain the integrity of the original starting route and its waypoint content.
Actual behavior
going from on route to off route and then back to on route seems to break communication for navigation instructions and voice instructions and arrival event. Also when on route is again restored it appears to have skipped several waypoints in the original route requested.
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 attached MAPBOX_BUG_SUBMISSION_07JUL20.txt and the OffRouteObserver logs. Reproduce the route using 25 waypoints and the listed SDK components, then trace the on-route/off-route/on-route transitions. Done means the original route and waypoints remain intact and navigation, voice instructions, and arrival events continue working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100