Cannot set signing for new Xcode project

Question

Created Feb ’16

Replies 2

Boosts 0

Views 4.8k

Participants 2

I have played around with Xcode's identity settings and the Keychain Access app in the past. Under Xcode's "Accounts," I have one Apple ID listed. It has a listing under "Personal Team," and Free under iOS and Mac. When I view the details, I have the "iOS Development" and "Mac Development" signing idenities active. I clicked "Create" for the Mac one, but there are no provisioning profiles on the bottom pane, just an option to "Reset" the signing identity, which doesn't fix things.

I created a new Xcode project,and selected "Apple ID" under "Signing." (It was "Developer" or Apple ID until I pressed the button and presumably it checked which on I had.) The status below it says "No code signing identities found" and "No valid signing identities (i.e. certificate and private key pair) matching the team ID 'XXXXXXXXXX' were found." When I press the "Fix Issue" button below that, I get a brief status bar then "The selected team does not have a program membership that is eligible for this feature. If you need assistance, please contact Apple Developer Program Support. https://developer.apple.com/support"

Looking at Keychain Access, I have a "Mac Developer" entry, with my e-mail but a different XXXXXXXXXX value. There is a private key under its disclosure triangle, but the main status bar says "This certificate has an invalid issuer." (It's not expired, though.)

Is there a way to fix this? Or at least reset everything so I can start over (with the same Apple ID)?

Boost

Answer 1

CTMacUser OP

Mar ’16

I somehow fixed it.

I removed the "Mac Developer" entry in Keychain Access with the different XXXXXXXXXX value. There is a "Apple Worldwide Developer Relations Certification Authority" certificate under the system keychain, but there wasn't an intermediate "Developer ID Certification Authority" certificate under the system-roots keychain until I downloaded it from the "Apple PKI" page (at http://www.apple.com/certificateauthority/).

In my Xcode project, I changed the team from my personal entry to "None." Then Xcode proposed adding my entry back. I pressed OK and Xcode made a proper signing. (Everything compiles, with the "Signing" saying "Apple ID".)

0

Answer 2

Valentin.Gubkin OP

Mar ’16

Dear Apple,

I have now wasted many, many hours of my life dealing with this same issue. Nearly every piece of advice online simply hasn't worked.

If these bugs with the provisioning system were new, I could understand it. But they aren't new bugs!!! I have been seeing these same old bugs with the provisioning profile system for YEARS now, on multiple (independent) machines. There is absolutely no excuse for it. The provisioning profile system in iOS is an absolute, completely, total freaking nightmare. What's worse is that you people seem to be completely and utterly incapable of fixing it. I've found convoluted procedures to fix this problem before, and I'm sure I will fix it with some stupid and unnecessarily complicated process to re-generate the provisioning profile (which is incredible since this profile is still totally valid and it should still work just fine....).

Please, dear GOD, fix these freaking problems with the provisioning system. Nearly every developer I know has wasted hours and hours of time in frustration with Xcode's idiotic and buggy provisioning profile system. It is the very definition of frustration. The wealthiest tech company on the planet has ABSOLUTELY NO EXCUSE to have the same old bugs year after year. Either fix it or just completely re-do it, ANYTHING to fix these ridiculous problems.

You know what? If I had developed the provisioning profile system for my own company, and it was riddled with so many bugs and glitches like Xcode's provisioning profile system is, I would be fired. Seriously, I am SO done with these stupid problems. It should really just work, and it doesn't.

1