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
[ios][release] GeneratedPluginRegistrant.m Module not found #43986
Comments
my fault |
Did you find a solution ? |
I am also looking for a solution. |
I would also like to know what solved the problem. I have the following error:
(and every next module when deleting location) |
I have got the same issue. |
I may have found the answer from this comment: Seems like by opening up the project by double clicking Seems strange that it would fix it. But I'm happy to have an Archived build now. |
Opening the project with Runner.xcworkspace doesn't work for me! |
On top of trying the xcworkspace trick, previously, I had tried deleting the Podsfile.lock, cleaning the project, changing the Podsfile min version to 9, or something like that. So it is possible some combination of those things plus the xcworkspace thing is the actual solution. |
Nothing worked for me. |
This was the only thing that worked for me:
I think I had ran |
@jaredanderton thanks. It worked for me too |
I fixed it the following way:
cd ./ios/
pod install
flutter clean # cancel by ctrl+c if it hangs up
|
This worked for me too... with the mention that #platform :ios, '9.0' line is Podfile... |
Really thank you! It works well for me! |
For me, it turned out the issue was that I was opening Opening |
Any update I'm facing the same issue, I'm sure that I open the ios/Runner.xcworkspace |
@davidgalarza did you try #43986 (comment) ? |
@TheOneWithTheBraid Yes I tried It but did't work |
@IamStupidMan @parvshkhan @rushabhshah065 I am stuck with exactly the same, did you found a solution to this? I will pay you a beer :D |
@IamStupidMan @parvshkhan @rushabhshah065 I figured it out for me. If you have this problem with cloud_firestore and you are using configurations, I am 100% this will fix the issue. I had multiple xcode configurations and in the scheme there was the wrong configuration associated with the scheme. In my case I needed to change it from Release to Release-development. Also make sure that alle the configurations on the left column are the once you created. |
I am also facing this issue |
I am also getting this error . Does anyone know about it? [!] A license was specified in podspec [!] Unable to read the license file [!] Unable to read the license file [!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target |
Did you choose the target as |
Also, are you building in different flavors? |
Yes i choose target as runner |
The above fixed my issue as well. Thank you! |
As it turned out, I was doing the same thing 🤦🏽♂️ -.... was super used to running the |
ok, here is what worked for me:
|
And I thought only google android is wierd! |
Finally after trying every possible solution this actually helped |
Is there anyway to specify the configuration from the command line? After a |
rm ios/Podfile work for me. |
Awesome !! Thank you!!! |
OMG! How did you find it??? |
Thank you, I have set that field to prod in my config ❤️ . |
I am experiencing the same problem and no one from above is working where latest version of Flutter, Pod and Dart is being used with stable channel. |
Solved following way: |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Hi,
I can run
flutter build ios
, even can work with debug mode on devicesBut when I want to release to store, Xcode cannot compile code.
Error: Module xxx not found
I delete it and got same error with the second module
Do you know why?
I use the latest version of Flutter and Xcode
Thanks
The text was updated successfully, but these errors were encountered: