Question The .p12 file failed validation against Apple CA chain.

Our old iOS credentials have expired, so we requested new credentials from our publisher.
Unfortunately, when uploading the new credentials, I get the following error:
The .p12 file failed validation against Apple CA chain.

I remembered that we already had this issue in the past, but our publisher fixed it by switching from iOS App Development and iOS Distribution certificates to Apple Development and Apple Distribution certificates.

I believe they're using the new ones this time, so what else could be causing this error?

 

Thanks for a quick reply!
Unfortunately the issue is still there.

As a side note, our .p12 file doesn't have a password. Can this be the issue?

 

The issue was on the publisher's end, the Mac, that they used to generate the credential files this time, was missing some certificates or something.
They regenerated the files on a different Mac and it worked fine for the Cloud Build even without the password for the .p12 file (so the password is not a requirement).

 

Hello, I'm following this tutorial in order to create the mobile provisioning file and the p12 file.

https://mzansibytes.com/2021/08/28/create-apple-developer-certificates-on-windows/

The process seems to work but when I upload the credentials I get the same error (The .p12 file failed validation against Apple CA chain).
Can you please help?

PS: I'm using wildcard App ID in the provisioning profile

 

Anyone? I also tested also with an explicit bundle ID and it didn't work

 

I also tried that and got the same error. I redid everything with this method: https://nima-jamalian.github.io/UnityWindowsiOS/#fb08b26d-0f2c-4861-87ae-3cfd895f9f09 and everything works like a charm.
Just don't forget to add only one / before the email address in the step to make cert signing request since the sample was wrong (it added // instead of / and an error appeared on openssl)

 

Thank you so much roseverte!
You saved me
Anyway it worked with two slashes on my side.. with one I receive an error

 

Lol. I don't know what has caused the error on my side then. Anyway, good to hear it's solved. At least for anyone who got error with two slashes they can try one, and for those who got error with one slash, they can try two slashes