-
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
No RouteProgress updates when shape format is geoJSON #2125
Comments
@kevinkreiser, do you know if MapboxNavigationNative supports GeoJSON-formatted route geometries, or only Polyline-encoded geometries? |
@1ec5 right now it only supports polyline6 geometries but it would be a very small amount of effort to add both polyline5 and geojson imho |
That would be desirable. We effectively regressed this functionality when migrating to MapboxNavigationNative, because even though the default changed to polyline6, there has always been an option to customize the format. |
The workaround is to leave the shape format as the default. The default value, A possible workaround in the SDK itself would be to hardcode
|
Mapbox Navigation SDK version: 0.32.0 (CocoaPods)
Xcode Version: 10.2.1
Tested on various iPads (simulator and real) with iOS 12.2
Hi everyone,
First of all, thanks for the solid framework you are providing, it's really good to work with!
While working with the results from the Mapbox Navigation API within the SDK, I discovered a bug:
If the
shapeFormat
parameter of theNavigationRouteOptions
is set toRouteShapeFormat.geoJSON
therouteProgress
object is not updated during simulation. In the UI this leads to not updating route statistics, missing voice commands, and not updating direction instructions. And as shown in the example below, all properties of therouteProgress
object are not updated.Through debugging I could only narrow it down to a not correct calculated
status
object inRouteController.locationManager(_:didUpdateLocations:)
. All called update functions afterwards can't read any progress from the retrieved status object.To reproduce the error just execute this modified version of the basic example:
The text was updated successfully, but these errors were encountered: