"Your account already has a valid Developer ID Application certificate"

The problem is that the "brand new machine" does not have the private key used to sign apps using your existing certificate. You can download all you like from the Member Center, but your private key is not there. It never leaves the machine that generated it - except when you export the developer profile, copy the resulting .developerprofile file over to a new machine, and import it using Xcode. That will move the associated private key.

If you didn't export your old developer profile before changing machines, should be no big deal - revoke and delete the existing certificates on the Member Center, go into Xcode preferences -> Accounts and delete any local copies of code signing identities and profiles. Then try and build again. Xcode should offer to "Fix Issue" - it would be nice if it actually explained what it was doing, but I believe it is emulating the old manual process. It generates a new private key, stores it in your login keychain on that Mac, generates a certificate signing request using that key, requests a new certificate and provisioning profiles from the server using the new CSR.

I just went through all this myself after my distribution certificates expired.

It should be a matter of just repeating the same process you did when you got started as a dev. That and refreshing individual app provisioning.

Once your new/fresh/valid dev & dist certs are in the keychain on your new mac, let Xcode take care of the rest. Be sure to give it a chance to use new, and not seek/apply old certs. Refresh individual app profiles with the new certs manually if needed. Do an option-clean build folder to force Xcode to absorb new certs, etc.

this did not help me.

Xcode Crashed upon deleting the profiles.

there was indeed a dialog that offerewd to fix the problem. It may have fixed the problem created by deleting the local profiles, But it did not fix the original problem.

KMT, when I started as a dev, there was no app store. When My apps were added to the App store, it had not launched yet. The process has changed a great deal since then, and there are fragments of the conflicting documentation, but nothing I have found that actually spells anything out.

That's unfortunate. It worked fine for me (Xcode 7.0.1 on Yosemite). You may have to do it the old way then - generate a private key and .certSigningRequest using Keychain Access, and use that to create your certificate using the web portal. If you do that, and download and install the generated certificate into your login keychain, as long as the private key is there Xcode should be able to find it.

Hence, me, asking for a link to clear documentation, rather than a broken automation.

the advice in the dialog does not in any way line up with reality.

which is an insane way to run a business.

quote: "You have a valid Developer ID Application certificate in the Member Center, but it is not installed locally. If your signing identity is installed on another Mac, you can export a developer profile on that Mac and import it on this Mac. You can also reset your current certificate."

in this block of text we find out that the member center has a "Developer ID Application certificate." Great. I do not have access to my previous developer profile, The particular machine that had a developer profile installed, ate itself and the hard drive, poof. So our only option is this bit: "You can also reset your current certificate." IF we're using english, then when the dialog says : "current certificate" it means that "Developer ID Application certificate." I know... it's a bit of a strecth that the only object in a different sentence is the implied object in a following sentence. I found the "Developer ID Application certificate" in member center. And when I click on it, there is indeed a revoke button. It's greyed out. you cannot click this button. So the advice: "You can also reset your current certificate." != true

I know it sounds like I'm harping on this. I am. I am not in the habit of following directions from an unvetted source, and I am unable to find a single coherent documentation of either: the process to fix my particular issue, or how to start out from scratch building the profiles and certificates that I need.

aside from this dialog, I have nothing that can guide the process. Apple has sucessfully protected the security measures they take, through obsfucation.

I get that I need a local file of vague and indeterminate origin, that matches a file that is on a great big server in the sky. and these two files, if they agree, mean that I am who I say that I am. the problem is that there are about 12 of those files. thay all have very unhelpful names, and Apple doesn't seem to know at times what the names are, in what little documentation exists. And for me... the system is Broke, and all I want to do is sandbox my app.

Hi, I just posted the following:

Error importing developer account in Xcode 7.1.1

Have you ever encountered an error when importing a developer account?

Cheers!

>The process has changed a great deal since then, and there are fragments of the conflicting documentation, but nothing I have found that actually spells anything out.

Being around so long now, this shouldn't be a surprise to you, I'd think - that and if things were going to change, they would have done so long ago. But yeah, what you said, especially from those of us that have been here since the beginning.

For me, tho, it's been a steady tail-chase, a 'situation normal', where Apple makes some things easier, then others harder...change for change's sake - a routine from Apple that doesn't seem to have improved over time, with consistent disconnects that seem to fall on deaf ears from our POV. From cryptic docs to forums a gradeschool wouldn't care for, it all combines to make things harder for devs, like it's one big long test to weed out the weak. No wonder devs hold parties when an app finally gets into the store...

For the dev tho, it's still build/provision app, then submit/wait & repeat as necessary. The details have changed, but the basics haven't.

Thus leaving all of us with anecdotal theories that if nothing else, demonstrate (a) our willingness to try to help and (b) how we feel your pain. So while we all find the process perhaps more of a black box than ever, we can at least take solace that we're not alone when running the same gamut.

Happy Holidays!

And as always, feel free to file bugs (link below right) against the docs, process, etc.

Ken

For some reason that does not work for me. Firstly, I cannot revoke the Developer ID Application certificate in the member center; the "Revoke" button is greyed out.

When I use the Xcode prefs and click on the "Reset" button next to that cert, all it does is to switch to Safari and drop me onto the main "Certificates, Identifiers & Profiles" page – nothing more specific.

Removing my Apple ID from Xcode and re-adding it does not change anything; both "Developer ID Application" and "Developer ID Installer" carry the unhelpful "Reset" button.

So, currently I'm stuck – I can't create a distribution-ready version of my app. Any news or further hints on this?

I stumbled on the same issue after moving to a new machine. Same thing, revoke was grayed out.

https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/Troubleshooting/Troubleshooting.html#//apple_ref/doc/uid/TP40012582-CH5-SW1

The Private Key for a Developer ID Certificate Is Missing

Optionally, contact Apple at product-security@apple.com if you need to revoke Developer ID certificates. Alternatively, you can continue to develop and distribute apps by creating additional Developer ID certificates, as described in Creating Additional Developer ID Certificates.

After creating new developer ID I was able to get rid of this error message. Before doing that I also revoked old certificates in member center and deleted them in Xcode by using right click and moved to trash, but not sure if this was required. Just tried to start from clean sheet.

My keychain error message reads " this certificate was signed by an unknown authority" and is, therefore not validated.

Any helpful solution. Its probably a no brainer but I just don't see it.

John in Pago Pago

That Creating Additional Developer ID Certificates link is golden. Many thanks