Łukasz Paczos

The points from https://github.com/mapbox/mapbox-navigation-android/pull/6466#issuecomment-1279080258 still stand - we require developers to interact with standalone instances of the views differently depending if they are the first one or not. For example...

> If there's a method to update the options why would a developer have more than one instance of MapboxRouteArrowView? There's no benefit. `MapboxRouteArrowView` is not a singleton, we can't...

This does look like the same issue but it would have to be a very short route (just 8 geometry points). @EricGeiler @Sridhar261990 do you perhaps have the `NavigationRoute#id`s of...

Thanks for checking @EricGeiler! The issue is only reproducible if there's at least one alternative present and would not be triggered by the code suggestion from https://github.com/mapbox/mapbox-navigation-android/issues/6403#issuecomment-1261184609. The change that...

Thanks for your input @dylan-chong, @JustSayBien and @tStaiger. Were you using emulators or physical devices? If the latter, could you let us know which phone models did you use for...

@andrei-cimpan your issue should be fixed with https://github.com/mapbox/mapbox-gl-native/pull/10899 that will be included in our `6.0.0` release. In the mean time, could you re-test this with `6.0.0-SNAPSHOT`? If you will still...

We don't have any additional changes in the pipeline, so we'll release a mapbox-java `v6.3.0-beta.1` today. Anyone could test it out independently or wait for it to be available in...

@TheNewCivilian makes the right point - this library only supports `polyline` and `polyline6` encoded geometries, even though the Directions API also supports the `LineString` (geojson) encoding. This is why the...

@langsmith I believe that this is the line that's throwing: https://github.com/mapbox/mapbox-gl-native/blob/482dfc501c57c1f1dd78213caf8a861e1bdf7d79/platform/android/MapboxGLAndroidSDK/src/main/java/com/mapbox/mapboxsdk/snapshotter/MapSnapshotter.java#L368, which is expected and could be fixed up on the Demo App side.

All of the pieces in the dependency tree of `crashlytics/ndk-reports` seem to weigh over 900kB (at least in the raw aar form) so I'd lean towards a specific crashlytics build...