You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have my own routing provider that mimics the Mapbox API, and it works well with an older version of Mapbox Navigation. Now, I want to migrate to a newer version, but I’ve encountered an issue: NavigationViewController now requires a NavigationRoutes object as an input parameter. However, I can't find a way to convert my existing Route struct—used in my Directions API wrapper—into a NavigationRoutes instance.
I'm really confused about how I’m supposed to use my custom routing provider with the new Mapbox Navigation controller.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! I have my own routing provider that mimics the Mapbox API, and it works well with an older version of Mapbox Navigation. Now, I want to migrate to a newer version, but I’ve encountered an issue: NavigationViewController now requires a NavigationRoutes object as an input parameter. However, I can't find a way to convert my existing Route struct—used in my Directions API wrapper—into a NavigationRoutes instance.
I'm really confused about how I’m supposed to use my custom routing provider with the new Mapbox Navigation controller.
Beta Was this translation helpful? Give feedback.
All reactions