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
Good to know, thanks! We could go back to individual podspecs, then offer bundled podspec later that installs all plugins. 🤔 Would multiple podspecs pose an issue once we have more plugins?
Yeah, I could see multiple podspecs being a royal pain to maintain. Even just pushing two podspecs for the navigation SDK project to CocoaPods trunk is a bit error-prone. (I always forget to run the slow pod spec update process between each podspec push.)
This plugins project would be the perfect fit for subspecs, but the root of the problem is that it’s incompatible with Xcode’s project model. It might still be possible to hack around the problem, as long as we’re really judicious about imports. That might mean eliminating PluginKit entirely.
Currently the Mapbox Maps Plugins can be installed via CocoaPods or manually. Carthage support should also be offered.
The text was updated successfully, but these errors were encountered: