-
Notifications
You must be signed in to change notification settings - Fork 222
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
Prevent transitive dependencies error using dynamic library #1227
Comments
Unfortunately, we have no plans to release a dynamic framework version of the App Center SDK. However, based on a thread, some users had success by adding
to their Podfile. I am not sure if it will work for you, but it might be worth a try. Edit: this thread may actually be more helpful. |
@mrcararia did you get it working with @achocron suggestions? |
@clpolet No, this not solve my problem. The issue occurs when I execute
|
Sorry for the late reply. HockeyApp and AppCenter are both static fat frameworks, they both have a crash reporter (another static fat framework) as dependency. The difference is the possibility to build HockeyApp from source and that's what you were using. Basically AppCenter doesn't have an AppCenter-Source pod to pull the source instead of the binaries into your project. This is not in our road-map for the transition to AppCenter but we'll still keep the feature request open in case it find its way into our road map. |
Any updates on that? |
As we do not have plans to add support for this feature in the next year, I'm closing the issue. |
Hello,
I would like to migrate from HockeyApp to AppCenter.
I have developed my own cocoapods library using 'HockeySDK-Source' as transitive dependency of my framework. Trying to migrate to AppCenter, cocoapods install end with error:
"target has transitive dependencies that include static binaries:"
Is possible to deploy a dynamic version of this cocoapod?
This is necessary to create a private pod using frameworks, needed when there are swift classes in Xcode project.
Thanks.
The text was updated successfully, but these errors were encountered: