mapbox / mapbox/mapbox-navigation-android
IndexOutOfBoundsException : getPointsToFrameOnCurrentStep
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
**Mapbox Navigation SDK version:** Mapbox Navigation 2.0.0 (GA)
### Steps to trigger behavior
Happening from time to time, not sure yet when it occurs.
Let me know what I can give you to help you reproduce the issue
### Actual behavior
```
Process: bike.cowboy.app.debug, PID: 17839
java.lang.IndexOutOfBoundsException: Index: 6, Size: 6
at java.util.ArrayList.get(ArrayList.java:437)
at com.mapbox.navigation.ui.maps.camera.data.ViewportDataSourceProcessor.getPointsToFrameOnCurrentStep(ViewportDataSourceProcessor.kt:189)
at com.mapbox.navigation.ui.maps.camera.data.MapboxNavigationViewportDataSource.onRouteProgressChanged(MapboxNavigationViewportDataSource.kt:478)
```
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
Read ViewportDataSourceProcessor.kt at getPointsToFrameOnCurrentStep (line 189) and trace its call from MapboxNavigationViewportDataSource.kt at onRouteProgressChanged (line 478). Investigate the intermittent out-of-bounds access reported for Mapbox Navigation 2.0.0 and establish a reproducible route-progress case. Done means this stack trace no longer occurs under the triggering conditions, with regression coverage where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100