mapbox / mapbox/mapbox-navigation-android
Navigation getRouteBufferGeoJson Error in sdk
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
java.lang.Error:
at com.mapbox.navigator.Navigator.getRouteBufferGeoJson (Native Method)
at com.mapbox.services.android.navigation.v5.navigation.MapboxNavigator.retrieveRouteGeometryWithBuffer (MapboxNavigator.java:99)
at com.mapbox.services.android.navigation.v5.navigation.NavigationRouteProcessor.updateRoute (NavigationRouteProcessor.java:64)
at com.mapbox.services.android.navigation.v5.navigation.NavigationRouteProcessor.buildNewRouteProgress (NavigationRouteProcessor.java:43)
at com.mapbox.services.android.navigation.v5.navigation.RouteProcessorRunnable.process (RouteProcessorRunnable.java:63)
at com.mapbox.services.android.navigation.v5.navigation.RouteProcessorRunnable.run (RouteProcessorRunnable.java:46)
at android.os.Handler.handleCallback (Handler.java:790)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:164)
at android.os.HandlerThread.run (HandlerThread.java:65)
Navigation SDK Version: 0.42.6
Facing this issue, I don't know how to reproduce the crash. but facing it on the production .
Kindly help me. How to resolve it.
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 at the Navigator.getRouteBufferGeoJson entry point and inspect MapboxNavigator.java:99, then trace the callers in NavigationRouteProcessor.java and RouteProcessorRunnable.java. Use the reported Navigation SDK version 0.42.6 and production stack trace to investigate reproduction conditions. Done means identifying reproducible conditions or a confirmed cause and documenting the resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, 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