Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Plugins should not require removing use_frameworks! from Podfile #9694
Right now the Google Sign In example app has removed use_frameworks! from its Podfile.
If this line is added back, the pod install step fails with the following error.
See firebase/FirebaseUI-iOS#34 for an example of other devs struggling with this issue.
A related issue is that the FlutterFire plugins are also written assuming use_frameworks! is not in the Podfile. For example, the Firebase Analytics example app fails when use_frameworks! is added back to its Podfile.
We should try to make our plugin system compatible with use_frameworks!, or if that's not possible for Google Sign In, at least make the Firebase plugins able to build with use_frameworks!.
We have a workaround (commenting out use_frameworks!), though it's not pretty, so I’m probably going to focus on other more pressing issues for the next few weeks. This issue is available if anyone else wants to investigate; it's possible that the answer is "just move to Carthage" in which case we can punt it.
Plus, Carthage doesn't automatically add(/remove) the dependent frameworks to your app project, which is basically the only thing we're using CocoaPods for (well, that, and letting plugins transitively depend on other frameworks).
Switching to Carthage means having to develop our own code for managing the Xcode projects, so it's not happening right now.
referenced this issue
May 19, 2017
Removed from step 6, Configure Google Sign-In on iOS section: