Skip to content
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

v2.1.1 #160

Merged
merged 1 commit into from
Dec 20, 2021
Merged

v2.1.1 #160

merged 1 commit into from
Dec 20, 2021

Conversation

1ec5
Copy link
Contributor

@1ec5 1ec5 commented Dec 16, 2021

Upgraded to MapboxNavigation v2.1.1, MapboxMaps v10.1.2, etc.

There are a lot of deprecation warnings due to mapbox/mapbox-navigation-ios#3261:

/path/to/navigation-ios-examples/Navigation-Examples/Examples/Basic.swift:26:41: 'init(routeResponse:routeIndex:routeOptions:directions:locationSource:eventsManagerType:simulating:routerType:)' is deprecated: replaced by 'init(routeResponse:routeIndex:routeOptions:routingProvider:credentials:locationSource:eventsManagerType:simulating:routerType:)'
/path/to/navigation-ios-examples/Navigation-Examples/Examples/Basic.swift:26:41: Use 'init(routeResponse:routeIndex:routeOptions:routingProvider:credentials:locationSource:eventsManagerType:simulating:routerType:)' instead

@Udumft, can you or someone else working on Core Navigation sketch out what you’d like to recommend to developers in terms of setting up a RoutingProvider?

/cc @mapbox/navigation-ios

@1ec5 1ec5 added the build label Dec 16, 2021
@1ec5 1ec5 added this to the v2.1 milestone Dec 16, 2021
@1ec5 1ec5 merged commit 7d7e20a into main Dec 20, 2021
@1ec5 1ec5 deleted the 1ec5-v2.1.1 branch December 20, 2021 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants