Reputation: 1941
On a new mac, I installed xcode and needed to set up provisioning for a hello-world project to deploy to my iPad.
NOTE: I am using the new FREE provisioning (do not have a paid Apple account)
ok? How do I get this resolved without flattening my OS back to factory and starting completely over?
Note: there are resolutions on SO that talk about Revoking the keys and generating new private keys from the Dev Console, like this one: How can I add private key to the distribution certificate?
HOWEVER, on a "free" account I have NO access to the Certificates section! I can't manage anything from the Dev portal online. I do, however, see xcode specifically set up to handle certs (see step 9-10 above) but it is not working. I really don't know where to go from here. I'm new to all things Mac and iOS and xcode. Frustrated. Thanks Apple, so much for a simple on-boarding experience on a simple hello-world app.
Upvotes: 21
Views: 26491
Reputation: 7164
I had this error and it occurred because I had moved to a new Macbook. Although there was a provisioning profile
on our Apple account and it was not expired, the private key was on the old Macbook
. So downloading and installing the profile did not help, as it was the private key that was missing. I revoked the provisioning profile and created a new one. I had the same issue for the distribution certificate
.
If you are concerned whether revoking and creating new certificates/profiles will affect existing deployed applications, take a look at this question and the answers. The bottom line is, for applications on the app store it will have no affect, but for Enterprise Distributions
, deployed applications will stop working if you revoke the provisioning profile. So if the application is on an Enterprise Account
, then it is best to try find the private key in the keychain of the Macbook where it was created.
Upvotes: 0
Reputation: 5966
After two bounties for this question which gave no results, I managed to find a solution to this problem.
Apparently, it was some keychain related problem.
To fix it:
Solution was found using the first comment here: https://github.com/desktop/desktop/issues/3625
Upvotes: 11