Fabian Keunecke
Fabian Keunecke
I see this same error on our app too. There exists a lot of Mapbox issues about this topic. The most mentioned cause is that the navigation view is growing...
> For example nearest point on line can be quite costly for larger geometries. I changed now the logic. The route is prepared and calculated on `setRoute`. This will reduce...
I would suggest now, that I clean up the code, add missing things like documentation and tests. And try again to give more performance to the drawing logic. Then I...
For a Valhalla sample see #119.
We also have the same behavior. Even with route snapping enabled. Thanks for linking the Mapbox issue, this will really helps! While we also need this fix, I will have...
> Don't know if we should set another thing to allow snapEngine to work as expected Yes! I made the same mistake. You need to change the following things: 1....
The SDK is showing a notification with current running navigation state. This notification is a foreground notification. The user can see, that the navigation is continue running and his location...
When we doing this, we should thinking about to upgrade our package names as well. What do you think @boldtrn?
I will finish the route eating this or next week. After that I will continue with this task.
The other ticket takes too long, I will prefer this change here. > Android 11 requires OpenGL 3 which not everyone wants. To overhead for the additional release should be...