Error: pod: Command failed with exit code 31 #43
Labels
awaiting response
If no response, issue will be closed
build issue
An issue related to build process
support
Support is being requested but not a necessarily a bug
Comments
|
v4.0.0 of this plugin removes the dependency on Make sure you're using When I run your steps to reproduce the issue, it works fine in my environment: console outputFYI I've just released v5.0.0 of this plugin which contains a major rework of the cloud messaging functionality to resolve existing bugs and add new functionality. |
dpa99c
added
build issue
|
@dpa99c thx for the feedback 👍 seems to have solve the above install issue. on the other side, I face the following error at build time, any idea? Same with v4.0.0 or v5.0.0 of the plugin I tried in a new project too like
|
|
Try setting the signing configuration for the project - error code 65 is normally related to app signing issues.
In my environment, your test case builds fine: console.log |
|
@dpa99c thx for the feedback and suggestion. I really tried multiple times with my real project, where my signing config is correct, removing platforms and plugins, adding them again, new build, etc. etc., setting and unsetting and setting again my signing profile, always land on this error no matter what If I remove the plugin it's ok but now even if I downgrade to v3.0.1, I face the problem too 😔 Pretty sure it's something linked to my setup, sorry for that |
|
Can you build your real project in Xcode? |
|
Right only if I remove the |
|
Are you able to build the example project? |
|
Just to be sure, with "change the package name" you mean changing the widget id in config.xml and removing/adding the platform again right? if so, nope same error with your example project |
|
Xcode v10.2.1 if it might be the problem |
|
yeah, that's what I meant. I have Xcode 10.2.1 and 11.0 beta 3 installed. |
|
|
|
Thx really appreciated 👍 I've successfully build and send to apple a version of the app this morning (with push in it). Double checked the certificates too, they are valid till mid 2020 In the meantime I created another app and updated POD |
|
If I build the project in Xcode it fails with the following error
|
|
OK, cool. Just trying to rule out possible causes 😀 |
|
@dpa99c I do really appreciate your help, specially because I'm pretty sure something is weird on my side |
Just to confirm - you are opening the Because it looks like it's failing to find Pod dependencies |
|
Yep
|
|
|
|
Thx! Ok so that POD error is gone. I have uninstalled, cleaned and reinstalled and updated POD to solve that |
|
And I'm able to build the test project 🎉 |
|
😎 that's a good working reference point |
|
And I'm able to build my real project too using the last version of the plugin both iOS and Android 🎉🎉🎉 So the key was to update cocoapods but also doing a clean install first Thx a lot for the support Dave, you are the best 👍 |
|
😄 no worries, I've learned something more too about Xcode and iOS build environments! Checkout the new features of v5 - I hope you can make use of them - the example project is a good demonstration of how FCM notification messages can be customised on iOS & Android |
|
I already know my client will love to be able to customize messages P.S.: I didn't found a way to add a msg to the donation I just sent you, so just wanted to say again thx and have a drink on me 😉 |
|
Thanks mate, enjoy going crazy with custom notification sounds and icons, etc. 😆 |
BUILD SUCCEEDED message not displaying on build ios project. |
|
Hey some one here could help me? I already made all those stuffs you guys saied, and my app's builds fine, but when i run it on emulator it's stucks on splash screen, the console still show things, but teh splash screen never outs |
same here |
|
I had this error when i had installed cordova-plugin-firebase-dynamiclinks. Then i found a workaround and updated pplatforms/ios/podfiles as: Then it's ok. I could install and build FirebaseX. Be careful about versions in podfile. |
|
What helped me was to specify the versions in package.json as follows: |
|
I still have this error: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hi Dave,
I tried to upgrade to the last version of the plugin and faced a conflict with the iOS platform. I tried then to reproduce the same behavior with a dummy project and I landed on the same problem respectively, when I try to install the last version of the plugin, I face the following error:
To Reproduce
Steps to reproduce the behavior:
Console Logs
Plugin Version
v4.0.0
Thx in advance and let me know if I should test or do anything.
P.S.: Rollback to plugin v3.0.1 meantime, doesn't face that problem with it
The text was updated successfully, but these errors were encountered: