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

Mapbox Maps SDK v10 Integration. #2808

Merged
merged 80 commits into from
Feb 20, 2021
Merged

Mapbox Maps SDK v10 Integration. #2808

merged 80 commits into from
Feb 20, 2021

Conversation

MaximAlien
Copy link
Contributor

@MaximAlien MaximAlien commented Feb 15, 2021

Description

PR brings initial Navigation SDK for iOS port to new Mapbox Maps SDK v10.

To see detailed list of changes see changelog.

Fixes #2794.

MaximAlien and others added 30 commits February 12, 2021 12:26
jill-cardamon and others added 12 commits February 19, 2021 16:18
* add delegate methods for waypoint customization, added temporary example usage of delegate methods in example app ViewController, removed NavigationMapViewDelegate conformance from CarPlayNavigationViewController
Remove Xcode 11 builds from Circle CI

Remove install dependencies step for Xcode 11
Remove MBNavigationAccuracyAuthorization workaround
Update package manifest to the latest dependencies and configurations

Test generic MapboxNavigation-Package target

Add codecoverage to an SPM job
…irections v2.0.0-alpha.1, Solar v2.2.0

Increased the PodInstall minimum deployment target to iOS 11.0.
Also consolidated example application installation instructions in the contributing guide.
Copy link
Contributor

@1ec5 1ec5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not that I’ve looked this whole PR over, but there’s no time to land a big PR like Friday night. 🎉

### Using Swift Package Manager

The MapboxNavigation framework [does not yet support Swift Package Manager](https://github.com/mapbox/mapbox-navigation-ios/issues/2629) either on the command line or in Xcode. However, if you are building a user interface from scratch, you can [install just the MapboxCoreNavigation framework using SPM](./custom-navigation.md#using-swift-package-manager).
The MapboxNavigation framework no longer supports Carthage. However, if you are building a user interface from scratch, you can [install just the MapboxCoreNavigation framework using Carthage](./custom-navigation.md#using-carthage).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is true, why is the section ### Using Carthage still present?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two separate frameworks, MapboxNavigation does not support Carthage but MapboxCoreNavigation continues to support it.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im still a bit confused, if MapboxNavigation does not support carthage why does it say:

Using Carthage

To install the MapboxNavigation framework using Carthage v0.35 or above [...]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The readme you’re looking at has been updated a couple times since this PR landed. Here’s the current version from the release-v2.0 branch, where we’re developing v2.0.0. The version on the main branch does still say that MapboxNavigation supports Carthage, because that’s true of v1.x.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, got it! :) Looks like the new version has a helpful qualifier

MapboxNavigation no longer supports Carthage as of v2.0.0-alpha.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backwards incompatible changes that break backwards compatibility of public API build Issues related to builds and dependency management. op-ex Refactoring, Tech Debt or any other operational excellence work. UI Work related to visual components, Android Auto, Camera, 3D, voice, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants