ChatGPT解决这个技术问题 Extra ChatGPT

missing private key in the distribution certificate on keychain

I have the following problem which I could not find a solution for anywhere. Basically, we have a company developer account (not enterprise) and so in order to submit our app, I requested from our team lead to send me the distribution certificate and create and send me a distribution provisioning profile.

With the developer profile, everything works good, but when I installed the cert and the provisioning profile, I did not see the distribution profile on Xcode, and nor do I have a private key under the dist cert in the keychain.

Does anyone know how to solve this? I read in diff places that I will need to revoke the certificate and create a new one, but I can't really do that since we have a bunch of apps in the company and I can't revoke it for everyone.

Sometime Private key is missing because we are trying to create Certificates with .CSR which were created on any other machine. So , make sure , your CSR file should also created on same machine where you are trying to create and install certificate..or you could use .p12 of certificates to avoid this issue
In my case I have two identical signing certificates in my keychain... It solved simply deleting one of them... Just in case...

N
Nirma

https://i.stack.imgur.com/vXRjU.png

Who ever created the developer credentials originally needs to go to the keychain on their computer and right click on the key(s) for private and public and export the key to a file. Then you just download that file on your computer and open it, and it will be added to your keychain.

You need to have both the private key (.pem file) and the certificate for your provisioning profiles.


To be more specific it's the .p12 file you need (exported)
@Nirma What to do if we don't have access to that computer from which developer credentials were originally created.
@NishadArora You'll have to create a new key to use. There's no way to use it without the the private key. AFAIK
@Nirma How to create New one
If it helps anyone, after having the public cert and private key installed (checked in Keychain Access and it was showing) I also had to restart Xcode to get it pick up the private key. Using Xcode 11.6 on OSX 10.15.5.
u
user9088454

As long as you still have access to the mac which was used to generate the original distribution certificate it's very simple.

Just use that mac's Keychain Access application to export both the certificate and the private key. Select both using shift or command and right click to export to a .p12 file.

Attached a screenshot to make it very clear.

On your mac, import that .p12 file and you are good to go (just make sure you have a valid provisioning profile).

https://i.stack.imgur.com/e3vAi.png


u
user9088454

To add on to others' answers, if you don't have access to that private key anymore it's fairly simple to get back up and running:

revoke your active certificate in the provisioning portal create new developer certificate (keychain access/.../request for csr...etc.) download and install a new certificate create a new provisioning profile for existing app id (on provisioning portal) download and install new provisioning profile and in the build, settings set the appropriate code signing identities


Here at my company is always a mess, nobody knows in which computer was created a certain certificate. Is just better to revoke and recreate
@user2387149 I'm here 6 years later to suggest CI/CD to do this kind of stuff and forget about distributon via xCode.
if i already downloaded a distribution certificate, then i revoked it then re request it again. should i remove the old distribution certificate?
@kafinsalim yes, since it was revoked and not valid anymore
J
Jamshed Alam

Delete the existing one from KeyChain, get and add the .p12 file to your mac from where the certificate was created.

To get .p12 from source Mac, go to KeyChain, expand the certificate, select both and export 2 items. This will save .p12 file in your location:

https://i.stack.imgur.com/jwjSE.png


R
Ramis

For person who are afraid on re-creating AppStore distribution certificate Apple documentation says:

Important: Re-creating your development or distribution certificates doesn’t affect apps that you’ve submitted to the App Store nor does it affect your ability to update them.

But it affects apps for Apple Developer Enterprise ecosystem.


it does if you have an enterprise account!
By "enterprise ecosystem system".... For ex. are you talking about if you work in a large company and 100 developers have that private key for that specific app?
@petrosmm Yes. It is special account for enterprise. With this account you can not publish application to AppStore.
M
Muhammad Owais

I lost hours and hours to resolve this issue, but it's fixed by just restarting MAC...


its woking for me
me too... instead i got it solved by restarting Xcode
It's 2022 and this is working on the latest XCode and MacOS
A
Alex Zavatone

In my case, I've lost all private keys in my keychain, new ones were imported correctly, but doesn't show the private key as well. The only thing that helped was generating new CertificateSigningRequest


M
Michael Yang

After you changed a Mac which are not the origin one who created the disitribution certificate, you will missing the private key.Just delete the origin certificate and recreate a new one, that works for me~


V
Vivek

When I try to upload iOS build to test flight then error was appear.

"Missing privacy key".

https://i.stack.imgur.com/xrCpi.png

Just 2 step for fix this error.

Remove old certificate from developer.apple.com Create new certificate from Xcode or developer.apple.com

My problem has been solved (I am using Xcode 9.4.1).

Please check, Xcode created new certificate.

https://i.stack.imgur.com/oaWb2.png


T
Travis M.

If you are creating your own Distribution cert, not using someone else's then this could help.

Spent quite a bit of time on this today, issues from not being able to create a SigningRequest to generating a distribution cert and not having it attached to my private key in KeyChain Access. These steps helped solve this for me.

If you are still having issues, revoke your current cert and start fresh.

Creating a new signing request

The Keychain Access > Certificate Assistant > Request a Certificate from a Certificate Authority is actually contextually aware of what you currently have selected when you launch it. Just to be sure that you aren't accidentally skewing your Request with some random selection, go to your Login Items and select the Apple Worldwide Developer item. Then launch the above Request and create the CertificateSigningRequest.certSigningRequest file.

https://i.stack.imgur.com/LEgUh.png

Go to Apple Dev portal, add new distribution certificate, upload your CertificateSigningRequest.certSigningRequest file and download the newly created distribution certificate. To import the distribution cert into your keychain, instead of just double clicking it, I recommend opening your keychain, go to "login/Certificates" area and drag and drop the cert here.

I had an issue where my cert would auto-install into the System area, instead of the login area where my private key existed and this caused my key not to be linked to the new cert.


m
mjb

At the Menu > Visual Studio (mac) > Preferences > Publishing > Apple Developer Accounts > [Select your apple id] > View Details > Create Certificate

To delete unused/invalid certificates, go to website: https://developer.apple.com/account/resources/certificates/list

delete any unwanted certificate there

Next is to create App ID (identifiers), go to website:
https://developer.apple.com/account/resources/identifiers/list

Next, go to website to create provisioning profiles:
https://developer.apple.com/account/resources/profiles/add

use the certificate to bind with your app id.

Next is to download the profiles: At your mac > At the Menu > Visual Studio (mac) > Preferences > Publishing > Apple Developer Accounts > [Select your apple id] > View Details > Download All Profiles


Š
Štěpán

I got into this situation ("Missing private key.") after Xcode failed to create new distribution certificate - an unknown error occurred.

Then, I struggled to obtain the private key or to generate new certificate. From the certificate manager in Xcode I got strange errors like "The passphrase you entered is wrong". But it did not even ask me for any passphrase.

What helped me was:

Revoke all not-working distribution certificates at developer.apple.com Restart my Mac

After that, Xcode was able to create new distribution certificate and no private key was missing.

Lesson learned: Restart your Mac as much as your Windows ;)


I
ISS

I accessed that certificate on apple's developer website and after downloaded it I opened it. Likewise, at open I got a little window asking if I wanted to add the certificate to keychain. Just tapped "add" and the "missing private key" error was gone.


P
Philipp Hofmann

My problem was that for whatever reason, the login keychain was missing in the Keychain Access. Xcode created a new certificate and added it to the login keychain but could not use it. Restarting the computer solved my problem.

https://i.stack.imgur.com/O8M5M.png


P
Priyanka

Check whether you are using Login or not to add the certificates, if you are checking in System at top left hand side then we wont be able to see it.

So drag and drop the .cer into login then check you are able to get the private key or not.


m
mfaani

Just to shed some light on this.

After I deleted my p12 certificate from Keychain. I re-downloaded my own certificate from Apple developer portal.

I was only able to download the certificate. But to sign you need the private key as well. So you either:

export both private key and certificate from Keychain to get it.

Upload a Certificate Signing Request and generate new certificates

That certificate by itself has no value for signing purposes. My guess is that the private key is created by keychain the moment you 'request a certificate from a certificate authority' but isn't shown to you until you add its tying certificate.


D
Dharman

I'm the creator of the key, but the key was attached to an expired Certificate.

To solve it I went to -> Xcode/Preferences/Accounts/"Account you use to archive"/Manage Certificates..

Then click on the dropdown menu with the "+" sign on the bottom left corner, and choose the type of certificate you need updated (mine was Apple Distribution).

This updated my new certificate with its key attached.


thats creating a new certificate question is different
M
Menon Hasan

Contact with the creator of iOS Distribution key and tell to export certificate and private key, then just download and double click it to access in your keychain.

https://i.stack.imgur.com/cZjdJ.png


M
Mechadroid

I assume you have switched device and trying to create a new certificate for your new device,

First revive the development certificate form the developers portal,

Go to xcode > preferences > accounts > select your apple id with the dev portal access > manage certificates > click on the team account > click on the little + button > click on apple distribution

Go to the apple developer portal , you can see a distribution certificate is created ,

Go to profiles create a new profile with the new certificate.

Download > install done


B
Benjamin Zach

I could resolve this problem by updating macOS and XCode.


This answer has nothing to do with the private key for signing certificates.