Open QuentinFarizon opened 3 years ago
ionut-tanasa
commented
3 years ago @QuentinFarizon i have the same issue but with latest stable version of cocoapods, which for you is working somehow.
not using bitrise though, locally on my mac.
I installed pod 1.10.2 and plugin 11.0.3-cli and i get the same build error
fun fact: if i build manually on xcode it works, from command line it doesn't.
QuentinFarizon
commented
3 years ago @ionut-tanasa If you just upgraded to plugin 11.0.3-cli, be sure to get the latest version of this plugin dependencies (ANDROID_PLAY_SERVICES_AUTH_VERSION, ...). As they are pinned in package.json, best to remove and reinstall this plugin, this will overwrite versions in package.json
martingarcia95
commented
3 years ago Hi @QuentinFarizon I had the same error when I tried to update 11.0.0-cli to 13.0.1-cli. After updated in my pakage.json (13.0.1-cli), I ran this command: pod repo update. It worked for me. You can look at the documentation and see the next steps here
Bug report
CHECKLIST
[x] I have read the issue reporting guidelines
[x] I confirm this is a suspected bug or issue that will affect other users
[ ] I have reproduced the issue using the example project or provided the necessary information to reproduce the issue.
[x] I have read the documentation thoroughly and it does not help solve my issue.
[x] I have checked that no similar issues (open or closed) already exist.
Current behavior:
I have a Ionic project that uses cordova-plugin-firebasex successfully since several months now. I use Bitrise to have reproducible builds, on iOS and Android. I'm using the "cli" version of this plugin (I tested on 11.0.3-cli and 13.0.1-cli)
I suddenly started to get build errors on iOS, with the same Btirise workflow, same code commit. See error log below. I pinpointed the issue to be the cocoapods gem version.
In my build workflow, I had a step to update cocoapods gem to the lastest version (`sudo gem install cocoapods --pre) Yesterday, it started installing version 1.11.0.beta.1, instead of the working 1.10.2.
I solved it by pinning the version to 1.10.2, and build is now green again. I have written this issue to warn others, and maybe this would require an investigation ?
Environment information