-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rerouting Issue in iOS SDK #2272
Comments
@luugiathuy suggestion to modifying SDK did the trick to stop rerouting but this problem definitely needs to be fixed. |
@soheilnikbin Do you have a sample project that reproduces the problem that you could share? If you don’t have a whole project, then maybe some of the code you are using? Finally, can you share a starting/ending coordinate for the original route that is being calculated? |
Unfortunately I cannot share the entire project here but I can share the code written for Mapbox navigation as below: So in this code I'm getting current location of the user to init route and than calling
And then here after getting route to create NavigationViewController. I've tested with simulating
This code tested on this coordinates This informations also might be helpful
|
You can access the function you require using mapbox-navigation-ios/MapboxCoreNavigation/RouteController.swift Lines 200 to 201 in 4ae1d62
|
Great, its working perfectly fine now.
This line of the code should clearly mention in documentation, or by default SDK should use |
This is a duplicate of #2125. You’re setting |
Navigation keeps on constantly rerouting after every route progress even though the user device location is on the same route. I thought Mapbox automatically handles rerouting only when the user leaves the current route. After I read this part of the documentation, I thought I needed to handle it manually.
Based on documentation, I used below code to handle rerouting manually but the code is deprecated.
So crash redirects me to this part of Mapbox SDK
but navigationService not containing userIsOnRoute function. Is there an alternative function I could use, or is this a bug?
The text was updated successfully, but these errors were encountered: