-
Notifications
You must be signed in to change notification settings - Fork 28.6k
The 'Pods-Runner' target has transitive dependencies #14161
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
Comments
Okay, after further investigation I now know why the sample project works, and not my actual project that depends on it through Pub. When generating a plugin template, the generated example Runner project was based on Objective-C : However the project I then created from Intellij is based on Swift : So the |
I also compared the AppCenter plugin to the Firebase plugin that are both implemented in Objective-C, with a dependency to a pod implemented in Objective-C. The only potential difference I see in Firebase/Core podspec, compared to AppCenter podspec that could be a problem is the |
cc @mravn-google and @collinjackson who might have more insights. |
@aloisdeniel We do seem to need |
FYI - I ran into this issue just yesterday when running my app on iOS for the first time in a while after having added in the google_map_flutter plugin. It turns out the fix was to replace my ios/Podfile with a newer one (I pulled the one from the google maps example). I believe mine was generated a few months ago when I started this project--I can't remember. In comparing it to the google maps flutter example Podfile there were quite a few differences and so it was easiest to just replace it. From this commit (flutter/plugins@20f9e7a ) I see that there is some work to clean up Podfiles in the plugins repo to make sure the latest is always used. |
related #12573 |
Ran into this problem, versioned down to cocoapods 1.4.0 and it resolved. Of course I'm running into another pod issue right now, but it's unrelated to this... |
@mravn-google, can you comment on your earlier statement "We do seem to need s.static_framework = true in podspecs when Swift is involved in the app and using CocoaPods 1.5.0 or later." please. Is that a "do need", "do not need", "maybe need"? This issue is still open... |
@RaduGrama As far as I know, we do need that declaration, see https://blog.cocoapods.org/CocoaPods-1.4.0/#static-frameworks It is used 14 times in the |
this is required for transitive dependencies. flutter/flutter#14161
this is required for transitive dependencies. flutter/flutter#14161
Fix issue discussed in flutter/flutter#14161
Proposed solution cames from flutter/flutter#14161
The 'Pods-Runner' target has transitive dependencies
For me, I deleted the |
It works... |
Worked for me too! |
I dont quite understand whats the override for this to work, I'm not able to use 1.4.0 version of Cocoapods, my project requires at least 1.10.0 |
Steps to Reproduce
Install my appcenter plugin and add initialisation code in your app :
The code works well with the local example generated with the plugin project template, but when installing with the dart package its doesn't work : I get the following error.
I first saw that in the local example project, the Podfile doesn't have the
use_frameworks!
command, so I removed it. But it fails too and the library doesn't seem to be present.Logs
Before removing
use_framework!
from Podfile :After removing
use_framework!
from Podfile :The text was updated successfully, but these errors were encountered: