-
Notifications
You must be signed in to change notification settings - Fork 4k
[firebase_core] iOS could not build module 'firebase_core' #3272
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
Facing same issue |
No amount of cleaning (flutter, pods, etc.) helped. Reverting to the penultimate version did the trick. |
Which version ??.. i am using latest one |
Are you stating that the above error about firebase_core was caused by a later version of image_cropper? If so, that's news to me. However, for those who just updated all their flutter dependencies and got the latest firebase_* plugins (pretty much all were updated around 8/17), just go to the version right before the most recent one (for each firebase plugin). For example, I had to revert mine to the following: firebase_core: ^0.4.5 |
Was talking about this issue 2020-08-20 16:25:08.109 xcodebuild[69982:2371607] warning: The file reference for |
Those look more like warnings to me. The OP is referring to these errors:
|
@dcchristopher @Kedar-27 the isuue is about the firebase_core, the logs about TOCropViewController are warnings generated by Xcode, but I insist the error is the following:
|
Running into the same error
|
Just updated my firebase dependencies and got the same issue. Tried every imaginable clean and rebuild but the error is still here.
|
I have time same issue, have you use package image_cropper? |
nope but I use crop: ^0.4.0 . |
I tried just removing the image cropper ..... the firebase issues still remain on iOS and prevent my builds :( |
Have you tried reverting to the version of firebase dependencies right before the most recent ones that came out just a few days ago? |
Here is a list of my current dependencies resulting in the error on iOS .... the # ones are the ones i used before and everything was working (besides super slow build times)
|
So the point I've been painstakingly trying to make is that for now you have to roll back to your previous firebase versions (the ones after the #). Once the firebase team fixes the issues introduced in their latest release I'm sure there will be an update in this thread. |
Certainly i can do that. This however remains another error i will not get rid off and this is build times of 10 to 30 minutes . I was actually hoping to get rid of these with the new updates. Therefore i will now wait instead of reverting. Thanks dcchristopher for your fast replies and support :) |
Seeing same issue here. I'm not using Image Cropper either. Has occurred since I tried to use firebase_ml_vision 0.9.6+2 Have cleaned, updated, rebuilt pods - the works. |
Would you share the exact commands and where you executed them ? flutter dir or iOS dir ? ... it might worth to try again. |
To confirm, is everyone here using a Swift iOS project instead of obj-c? |
Yes my friend . |
Is it possible to change the projects in flutter ? I use base configuration with VS Code ... |
Bit of a weird long shot, but can some try remove this line locally and clear all caches etc and rebuild (ensuring that pod install does get run as part of the build): https://github.com/FirebaseExtended/flutterfire/blob/master/packages/firebase_core/firebase_core/ios/firebase_core.podspec#L29 If you look in |
Hi... i think i can try it... dont know however if i will execute it right ... but a remark ...
|
@andrsdev in my CI / CD it actualy takes it as critically ( using AppCenter to build ) :( ... might need to wait till this can be solved... but at least i can continue testing |
Thank you so much. I faced the same issue last night. This morning I was reading this and then my issue is gone. |
Catching up with this issue, has someone proposed a solution? (I posted a duplicate issue while trying the example code at pub.dev) On a side note I'm puzzled by @Salakar saying "You shouldn't be adding the Firebase pods to your Podfile, they're automatically added transitively through each FlutterFire plugin." Maybe google documentation hasn't been updated because I can still find documentation there that says, for example, to "Add the dependency for Firebase Authentication to your project's Podfile", and when adding an iOS app in Firebase the procedure shown is still to import the Firebase SDK in AppDelegate. Have these instructions changed? |
Thank you @andrsdev ,Adding the dependencies in Podfile solved my issue. my podfile :
|
I got that issue when I used flutter_image_cropper. Then I forked the flutter_image_cropper with an older version (v1.2.3), change the following line of ios/image_cropper.podspec then go back to your flutter's pubspec.yaml, and use git dependency |
downgrading all firebase plugins to build before August 17 worked form me. |
Would someone be able to provide me a repo that I can clone that reproduces this, then I can take a proper look. I tried to reproduce this myself (#3272 (comment)) but everything worked as expected 🙈 |
@Salakar Have you tried creating a new flutter project downgrading flutter version to 1.17.5 or v1.12.13+hotfix.9? That could be the key to reproduce this issue, since most of current apps were created with older flutter versions. UPDATE: UPDATE 2 |
To test the proposition that pods are added transitively, as mentioned by Salakar, I removed With all those iOS-specific imports removed, it builds successfully in Xcode! When I build the iOS project in IntelliJ, it does not work and shows this output:
(I'm using Flutter Channel stable, 1.20.2 and Dart version 2.9.1.) |
Just wanted to say I had this exact error and I fixed it like @Beautylivery said. The crux of it was to move my pod declaration after Adjusting my podfile like below fixed the build error for me: target "Runner" do
pod "Firebase/MLVisionBarcodeModel"
use_frameworks!
use_modular_headers!
// ... |
@acoutts thanks for confirming what works. With the following I was able to build to the iOS emulator from within IntelliJ. In AppDelegate.swift I removed In the Podfile I put
|
With the new federated plugin setup / FirebaseCore, you do not want to add anything to your podfile like that as it is all managed by the plugin(s). You can override specific version numbers like this: In my case I have added MLVisionBarcodeModel because that's a separate lib which still requires that step. |
@acoutts You are right! I think we can close this issue, but it would be helpful to update firebase_ml_vision documentation to clearly state that those pods must be added like that. |
If I leave these out of the podfile, the build fails:
This isn't consistent with the instructions here to not add anything to the podfile. |
@fogelfish are you using firebase_ml_vision? or adding other pods (not firebase related) to the podfile? |
Also try a |
I recreated the project from scratch and I can now verify that there is no need to add the FlutterFire pods to AppDelegate.swift or the Podfile. I've been simply working with the example code at pub.dev for firebase_core, unchanged by me and no other pods involved. |
@acoutts By the way, the problem I faced while building was "The 'Pods-Runner' target has transitive dependencies that include static frameworks" and while it didn't mentioned firebase, upgrading it with fixed Podfile solved it. |
Thanks @andrsdev your solution worked for me! |
Hi guys, I don't use any methods above. But these steps fixed the issue for me. Hope they will help you too.
|
This helped me |
Describe the bug
Updated to firebase core 0.5.0, and new plugin versions.
To Reproduce
Expected behavior
A successful build for the iOS simulator
Flutter doctor
Complete output
The text was updated successfully, but these errors were encountered: