GCM certificate configuration not working or iOS

问题:

I am facing one issue when I am trying to confiure the GCM and getting configuration file. When I am trying to upload the production certificate over the GCM portal it says "Bundle Id in certificate doesn't match with Bundle Id you entered". I verified already for the same. Still no joy. Anyone help plz.

回答1:

I tried it with both Development and Production .p12, both worked for me.

You need to make sure you generate a correct .cer certificate file from your Bundle ID, and need to make sure you export the correct .p12 file from your Keychain Access. You can view the sample steps in this page.

You need to make sure the iOS Bundle ID you input in the GCM portal. (I use mine com.ziyang.samples.quickstart.gcm)

matches the Bundle ID in your Apple Developer Portal. (I use mine com.ziyang.samples.quickstart.gcm)

If I miss typed the iOS Bundle ID in the GCM portal, it will show the below error:

回答2:

For my case, I have to export a cer not a private key.

回答3:

I had the same problem but for different reason. It turns out that the .p12 file has something wrong. If I export .p12 file from Keychain Access by selecting both certificate and key and export 2 items together, it doesn't work. I need to export the certificate and key separately and merge them later. Use terminal to merge two files:

cat cert.p12 key.p12 > cert_merged.p12

回答4:

I have been getting same exact problem in Firebase (FCM).

The only solution which has worked for me, which I found by hit and trial is while exporting the Cert as the P12, only select the Cert but don't select the Key.

You will still be able to export only the Cert (without the key) as a P12 file and set the password in a similar way.

Now uploading this P12 file with the provided password works for me.

Make sure to export only the certificate not the key... by clicking on the triangular/caret dropdown icon and deselecting the key

回答5:

Make sure you're using your APNS certificate and not your regular development or production certificate. Just spent an hour on this until I realised my mistake!

回答6:

if you sure you set the right bundle id You can solve it by:-

1-Export only private key as p12.

2-Export only CERT as p12.

3-Export CERT with private key as p12.

and try one by one to solve this issue

回答7:

Please select the Certificate instead of the key in the Keychain Access while exporting it to .p12.

回答8:

A Password is Required when exporting the development certificate. The Development certificate would not upload with any of these suggestions until I added a password. I was, however, able to upload the Release certificate without a password. I also used the suggestion of @Sur Max to only export the certificate and not the key.