-
Notifications
You must be signed in to change notification settings - Fork 95
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
Adds subspec workaround. #23
Conversation
Tested end to end here: Steps to implement this solution: Podfile
Run pod install In your app, you will see that Pods > Segment-Firebase is empty. Right click and Show in Finder You will see the Classes > SEGFirebaseIntegration files. Then update your bridging header:
And follow the normal steps to import the integration into your AppDelegate.swift:
|
If the customer has to copy the files for this integration into their project, what purpose does I think they could just copy those files and do |
@f2prateek It's just convenient and still allows them to "pull in" the files from a Cocoapods |
Gotcha. |
🎉 Congrats 🚀 Segment-Firebase (2.2.0) successfully published
|
Do we need the full |
This workaround to Cocoapods Static Library/Framework.
The limitation occurs when an application is built in Swift, you are including
use_frameworks!
in your podfile, and are using a transitive dependency that is provided as a static library or framework.The current workaround (as outlined in this subspec) is to copy the integration code manually into your project, then depend on Firebase directly. Instead of importing the integration from our library you would import the integration from your local copy. This eliminates the transitive dependency from the App -> Segment-Firebase -> Firebase to App -> Firebase.
Tested with the following configurations
Without
use_frameworks!
With
use_frameworks!
CC @TeresaNesteby