-
Notifications
You must be signed in to change notification settings - Fork 312
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
[Bug]: v3.0 Does not support cocoapods? #4646
Comments
Can you provide the latest version? I expect it to be the latest, not concerned about stability. MapboxSearch MapboxCommon MapboxMaps MapboxCoreNavigation, Because I have used it all |
Thank you for bringing this issue to our attention! CocoaPods support is indeed on our roadmap for Mapbox Navigation version 3. Unfortunately, we do not have a specific timeline for its implementation at this moment. We will keep you updated with any new information as soon as it becomes available. |
I'm trying to create a react native/expo wrapper for the navigation SDK and the lack of cocoapods is a real pain point in the process. Support for it soon will be greatly appreciated! |
I’m trying to integrate with expo as well, have you found any workaround to make it work? |
Yeah, but it's an ugly process. See the bottom of the readme here https://github.com/YoussefHenna/expo-mapbox-navigation. But also, you should be able to use the package as is. Although I've yet to add a bunch of features, and there's a know bug with the latest version on Expo 50. |
Also trying to integrate the .xcframeworks with cocoapod as vendored frameworks throws this error in xcode |
I was also trying to integrate with Expo. I ended up using different SDK versions per platform:
It works, however, I would like to align those versions as soon as Mapbox adds support for cocoapods in v3. |
I got it working with expo and v3.3.0, you gotta build the frameworks from source |
@kried Any updates on when we can expect this? It's blocking proper react-native/expo integrations and development. |
Mapbox Navigation SDK version
v3.0.2
Steps to reproduce
Expected behavior
Installation successful
Actual behavior
error
Is this a one-time issue or a repeatable issue?
repeatable
The text was updated successfully, but these errors were encountered: