This does not appear to be a valid .p12 file. Perhaps it's been corrupted.

[Lohoris2_1]

I’m getting this error message while trying to setup to cloud build for iOS.

I’m creating this .p12 file from Keychain Access → Export “private key”.

Is there some way I can check if it’s really being created currupted my-side?

[David-Berger]

Which error message do you get?

I probably can try something like

openssl pkcs12 -info -in keyStore.p12

[Lohoris2_1]

@David Berger

Which error message do you get?

I get “This does not appear to be a valid .p12 file. Perhaps it’s been corrupted.” when I submit it on the unity cloud configuration page.

@David Berger

Which error message do you get?I probably can try something like

openssl pkcs12 -info -in keyStore.p12

This gives me no errors, so I can assume the key is fine:
MAC Iteration 1
MAC verified OK
PKCS7 Data
Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048
Bag Attributes
friendlyName: Lohoris@Goblinsama S.r.l.s. dev key
localKeyID: [abridged]
Key Attributes:

[David-Berger]

Which browser do you use, could you try a different one. Does this message appear directly on selecting the file, or once you entered the password and press next to proceed? If it is after you entered the password, would it be possible to change to password to something easy e.g. abcd to check if it might include character which might cause trouble?

[Lohoris2_1]

@David Berger

Which browser do you use, could you try a different one. Does this message appear directly on selecting the file, or once you entered the password and press next to proceed? If it is after you entered the password, would it be possible to change to password to something easy e.g. abcd to check if it might include character which might cause trouble?

I used Chrome, tried again with Safari and I got the same error.

It happens after I pick both files (provisioning and p12), enter the password, and click “save settings”.

I’ve tried both to have a simpler file name and a very simple password, and it always failed in the same way except just once where I got a “Curl error” after a while. I guess it was just a random occurrence, since using the same file again with the same password yielded the first error on next tries.

[David-Berger]

You need to export the certificate, not just the private key.
When you run the openssl command, there should be a big section that looks like:

-----BEGIN CERTIFICATE-----
….
-----END CERTIFICATE-----

Could you please try this and let us know if it works then properly?

[Lohoris2_1]

@David Berger

You need to export the certificate, not just the private key.
When you run the openssl command, there should be a big section that looks like:

-----BEGIN CERTIFICATE-----
….
-----END CERTIFICATE-----

Could you please try this and let us know if it works then properly?

Ok, using the certificate it works, thanks!
I was mislead since the certificate contains only my name, while I was searching for my company’s name instead…

[fullbrickstudios]

@Lohoris2_1

Ok, using the certificate it works, thanks!
I was mislead since the certificate contains only my name, while I was searching for my company’s name instead…

How do you did that ?
I am still getting this error

[Lohoris2_1]

@fullbrickstudios

How do you did that ?
I am still getting this error

Unfortunately I have absolutely no idea, and I haven’t exported anything to iOS ever since.

Based on my own comment, it looks like I was using the wrong certificate.

[system]

Hello,

@fullbrickstudios

How do you did that ?
I am still getting this error

In key chain you need to select both : certificate + private key.
Then export the 2 elements in the .p12

[joshuacwilde]

easier method is to go to Keychain Access, then “My Certificates” tab. Click the cert and export it to a p12 file. This will export both the cert and key.