Nastassia Makaranka

Hi @faliinitse Could you please share the Navigation and Directions SDK versions you are using? Is the problem reproducing consistently during the reroute? Would it be possible to share the...

Hi @faliinitse Thank you for the recorded data, we were able to reproduce the problem. We will fix the crash in upcoming SDK releases. But the response [routeDataJsonAfterRerouting.txt](https://github.com/mapbox/mapbox-navigation-ios/files/14257987/routeDataJsonAfterRerouting.txt) seems to...

@faliinitse This exact crash won't happen on Android, but please validate the response to the [Directions API](https://docs.mapbox.com/api/navigation/directions/) response scheme to avoid incorrect response parsing. E.g. the response does not contain...

Hi @faliinitse The fix should be available in [v2.18.0](https://github.com/mapbox/mapbox-navigation-ios/releases/tag/v2.18.0) with NavigationNative v204.0.1

Hi @Andybat99 Please check that you have correctly configured your secret token https://docs.mapbox.com/ios/navigation/guides/get-started/install/#configure-credentials Please try to clean the Xcode DerivedData and SPM cache and try to resolve dependencies once again.

Please check that you have the `.netrc` file in the system in the location `~/.netrc`. From the logs you attached in the issues description it seems like all 4 Mapbox...

Hi @Andybat99 Please try [v2.18.0](https://github.com/mapbox/mapbox-navigation-ios/releases/tag/v2.18.0) release, which removes the dependency on MapboxMobileEvents

Hi @inzamaminvozone Thank you for your report. Unfortunately, we were not able to reproduce the issue. I can see on the screenshots the messages in the Ukranian language. The Navigation...

Hi @santoso8118 Let me clarify if this issue is a duplicate of #4450 or a different issue. Could you provide a stacktrace for this crash, how often does it happen?

Hi @nik-bplx > [-122.023306, 37.360792], [-122.070464, 37.381085], [-122.069909, 37.407302], [-121.974796, 37.353317] It looks like we need more information to reproduce the issue, we were not able to reproduce the issue...