It has been awhile since I have updated my app in the App Store, so I renewed my Trigger.io subscription.
My Provisioning Profiles and Certificates are all currently expired so I generated a new CSR according to the Trigger.io documentation using the "certreq -new request.txt" command.
The problem is you can no longer upload the CSR file to https://developer.apple.com/account/ios/certificate/create to generate a new certificate. You get "Invalid CSR - Select a valid Certificate Signing Request". This used to work for me. Did Apple change something on their end? I even tried changing the file extension to .certSigningRequest, and it still doesn't work.
Please help. Thanks.
Related
While configuring certificate for Push Notification on my ios build of cordova project using OneSignal, the certificate is getting rejected every time I'm trying to configure it.
I've followed steps mentioned in https://documentation.onesignal.com/docs/generate-an-ios-push-certificate
I've tried using OneSignal Provisionator Tool, and generated certificate using KeyChain access as well without any result.
You can test APNS connection with this script:
https://gist.github.com/greencoder/16d1f8d7b0fed5b49cf64312ce2b72cc
This script requires your key and certificate in pem format. To convert from p12 use
openssl pkcs12 -in PushCertKey.p12 -out PushCertKeyNoCrypt.pem -nodes
Ok, I contacted the support and here is a troubleshoot for future reference:
1.With your newest certificate, try renaming it to something different than previous certificates and then uploading it again.
2.Also, some users have reported that their security software blocks this from uploading, please make sure that is not the case.
3.Please make sure you are uploading a .p12 Push Certificate and not a Distribution Certificate or anything else besides a .p12 Push Certificate.
Just click the "Choose File..." button if this is your first time uploading like this: https://imgur.com/a/JQQya
Or the "I'd like to replace my production .p12 certificate" check box if you are replacing the certificate like this: http://imgur.com/a/hRIqJ
4.You can generate one with OneSignal provisionator tool or if you have been and it is not working, you will need to try to generate one manually.
You can follow this Generate iOS certificate doc step by step to generate certificate, I followed it and uploaded it successfully.
If it is still not working, you can contact them providing the p12 cert to them with password and OneSignal AppID. they may upload it for you as soon as they can.
OneSignal had a service issue that caused certificates to be incorrectly detected as invalid. It is now fixed, as noted in this status update.
I am currently testing an app in TestFlight and need a production APNs certificate in order to test Notifications in Firebase.
I have followed all of the steps in this video and successfully configured the development APNs certificate:
https://www.youtube.com/watch?v=LBw5tuTvKd4
I've also checked that my steps following the Firebase support guide. Although I note that the Apple Developer site has changed slightly since this guide was written:
https://firebase.google.com/docs/cloud-messaging/ios/certs#configure_an_app_id_for_push_notifications
I have generated a production APNs certificate at developer.apple.com using the same method as the development certificate but when I try to upload the .p12 file to Firebase, it gives me the following error:
"The certificate environment did not match. Ensure that you got the right development or production APNS certificate."
I'm definitely uploading a .p12 generated from a production APNS certificate, is there something else I need to do for a production certificate?
Solved. The mistake I was making was that I was exporting the "private key" part of the certificate in Keychain Access instead of the "certificate" part. As soon as I re exported the .p12 using the correct row in the list - it worked.
Images to illustrate below credit iOS
Correct method:
try this
make .csr file and download cert from developer.apple.com
while exporting select private key and certificate both at a same time and export to .p12 with any passphase.
upload tht .p12 file on firebase console.
Thanks
Don't select private ket in key chain, directly select certificate and create production certificate.
1) Don't select private ket in key chain.
2) Directly select certificate and create production certificate
I am facing the same problem and i have tried all above mentioned solution but nothing works for me than i delete certificate from keychain access and again download certificate and install it than export and try to upload it. It works for me.
When I tried the solution suggested here, nothing works (This probably means I am doing right). I solved this issue by replacing Chrome (The application is running for a very long time) with Safari (I invoke the application just for this purpose) for the upload.
That means, if restart Chrome might also work.
FYI.
In my case I wanted to upload a production certificate to Firebase, and after trying everything I finally realized that I had created a development certificate on iOS Developer...
There might be an inssue of semantics in some cases, so pay attention to meaning.
When you have to upload the certificates in firebase console there are 2 boxes with placeholder text which read:
1. No development APNs certificate
2. No production APNs certificate
In my case, I had understood that I must not upload a development APNs certificate in box 1. Actually, firebase meant that no development Apns certificate has been uploaded yet and that I could upload my certificate.
I was having this problem after my previous p12 had expired, I was trying to upload as a new certificate and was getting the “does not match the current environment” error but it uploaded fine once I updated the expired p12 with the new p12 instead of trying to upload the new one alongside the expired one.
I am trying to export an .ipa file from XCode 6, and I get an error like this:
The dialog says "revoke the current certificate and request one again", but I don't see a way to do that. The Apple Troubleshooting page for this issue suggests I should click the "Revoke and Request" button, but I don't see one.
How do I revoke the old developer certificate and request a new one?
I suppose that the certificate is a distribution one, not development one. It seems that you have installed your iOS Distribution certificate in another Mac. And, it seems again that you download this certificate from Apple portail and import to your new machine. Of course, the simple import is not valid. Cause a certificate requires a private key to be associated with.
Then, you have 2 solutions:
Export your certificate from old machine (include private key) then import to your new machine. I recommend it.
Revoke this certificate if you do not use anymore on old machine. Then, from new machine, create new request signning and request again the distribution certificate.
Visite your account, in distribution certificate section, click to the certificate to revoke, you will see "Revoke" button.
Beware that all provisioning profiles created with this certificate will be invalidated.
Just for info, you have only <= 2 distribution certificates to be created.
I am trying to upload a binary of an App so that I can test out in app purchase.I can run the Application on intended iOS device which mean the development profile is working fine. But when I try to archive the file I get the error as shown in the image. Since i cannot import the private key associated to the profile show in the error I want to generate my own certificate using keyChain. So I created the certificate but I can't find the option send invite to a distributor or upload a certificate. My profile status is Admin. What should i do.
You should revoke your distribution certificate in your account.
So that it ask the .cer keyfile in your account again. You can create .cer file in your keychain go to Request a Certificate from a Certificate Authority and give your details that your mail id etc. so that it will create .cer file and in developer.apple.com , you can upload the cer file once you revoke your distribution certificate so that it will generate the certificate which can be installed in your system.
I am currently fixing bugs for a client who had the iPhone app made by someone else.
I think i have to use the clients distribution certificate to upload the binary of update..
I downloaded the distribution certificate but Xcode is complaining valid sign identity not found.
I know it is an issue with the keychain .. i don't have accces to the keys of the original developer..
how to proceed?
Invalidate the certificate
Create a new one
Create a new distribution profile using the new certificate.
Install that profile in XCode
???
Profit :)
If use certificate from another person then you are in need of private key. Without private key, you will be unable to sign binaries in Xcode and test your application on any Apple device. Try to request a .p12 file from original developer for this certificate or create new one yourself.
Delete any certificates you might have from the provisioning portal
Create a new Certificate Signing Request on your mac
Upload that request to the Provisioning portal to generate a new certificate
Associate your existing provisioning profile to the newly generated Certificate
Add the new provisioning profile to XCode
Compile your app :-) Done.
This will not delete any app details. This is just creating a new certificate. You will still be able to use all your old details. So dont worry.