y

You already have a pending certificate request

Apple distribution certificates but their private keys are not installed

In the Member Center, you have a valid iOS Distribution certificate, but it is not installed locally. You can export a developer profile from another Mac and import it on this Mac if your signing identity is installed on that Mac. You may also get your existing certificate revoked and a new one issued to you.
I only see one certificate signing identity “iOS Creation” when I go to Preferences > Accounts > View Details. What is the procedure for adding the current Distribution certificate? I assumed that simply putting it on my Keychain would suffice. When I try to drag a certificate from my Keychain into the View Details section’s signing identities, it doesn’t work because I can’t drag it in there.
Is your apple id a part of the developer team in Xcode / Preferences / Accounts? It may default to “(your name) (Personal Team)” in the bottom right corner of the Accounts tab under team name, but there should be another option “(your team’s name)”. So, if your team is called “The Awesome Team,” you can pick “The Awesome Team” under “Team Name,” not your own name.

Missing private key for signing certificate

This client has their own bundle ID for this unit, and it’s likely they have their own provisioning profile as well. But it’s possible that Apple is matching the package ID regardless of the developer account used for provisioning.
I was able to fix the problem by changing the app’s package ID and manually going through the provisioning process, but I’m not sure if this is a common problem, so I’m not sure if this post will help anyone.
I recently discovered that removing my account from Xcode and then signing in again fixed the issue. As part of that process, I did revoke my current certificates and request new ones. I didn’t use an existing profile as a template.
You may have an older Mac with the allotted development certificate already depleted. You’ll need to export the developer profile from that computer in that situation. If you no longer have access to that phone, you should consider invalidating the certificate and requesting a new one.
Another choice is to double-check your project’s build settings to make sure it’s searching for the correct certificate. In my experience, these environments often make decisions on their own, so double-checking that they’re what you expect will help.

Maximum number of certificates generated

Problem: As of Xcode 6.3, I am no longer able to perform automated system provisioning for one of my clients. Is anybody else had a similar problem? My client has their own bundle ID, and there’s a chance they have their own provisioning profile for this system as well. So, regardless of which account is being used for provisioning, I assume Apple is matching up with the bundle ID. I was able to solve this problem by changing the app bundle ID and manually finishing the provisioning process.
Solution: I can assure you that this problem is much more widespread than you can believe.
Solutions to this problem include:
I usually find that changing the settings in Xcode and then signing out and back in fixes the majority of my problems.
You can also try an older Mac that has already used up the one production certificate allocated to it. This will fix your problem if you export the developer profile from that machine. You can also double-check the project’s build settings to ensure that it is searching for the correct certificate. It is normal for settings to make their own decisions.

Your account already has a valid ios distribution certificate

This client has their own bundle ID for this unit, and it’s likely they have their own provisioning profile as well. But it’s possible that Apple is matching the package ID regardless of the developer account used for provisioning.
I was able to fix the problem by changing the app’s package ID and manually going through the provisioning process, but I’m not sure if this is a common problem, so I’m not sure if this post will help anyone.
I recently discovered that removing my account from Xcode and then signing in again fixed the issue. As part of that process, I did revoke my current certificates and request new ones. I didn’t use an existing profile as a template.
You may have an older Mac with the allotted development certificate already depleted. You’ll need to export the developer profile from that computer in that situation. If you no longer have access to that phone, you should consider invalidating the certificate and requesting a new one.
Another choice is to double-check your project’s build settings to make sure it’s searching for the correct certificate. In my experience, these environments often make decisions on their own, so double-checking that they’re what you expect will help.