Valid signing identity not found solution for iOS development on Mac OS X (loss of original IDP private key)

Preface:

I just changed the mini to macbookair, and I have been developing it on the Mini. Before I changed the air, the first project was just launched, and the first application for testing and certificate publishing were all completed on the mini, due to carelessness, after changing to air, I cleared all the mini and sold them in the second hand. I deleted the previous development certificate, in fact, it should be backed up and exported ....

As a result, log on to the website on the new air:

You want to download the certificate you created before, but after double-clicking the download, you will find in the key string:

I always felt a little less, and finally found that the certificate we downloaded was not a small key on the computer, which was called a private key.

Download the project's provisioning file from the provision tab of the website to see how it works:

Double-click the downloaded file, open xcode ---- organizer, and check the status in provising files:

The system cannot identify it. That is to say, if we lack the personal key of the previously developed computer, we will generate a certificatesigningrequest according to the online debugging process of the first real machine at that time. certsigningrequest: Upload the private certificate key !!

Have you ever met me like this, but now, the computer you used to develop cannot be found, that is, it cannot be exported.

Solution:

I. Use the original certificate

Find the certificate from the previous PC, and export-import it. This is the easiest and easiest way to save trouble!

1. Open the key string access tool on the original computer, find our iPhone developer Development Certificate, right-click to export

Note that the key must be included to export p12.

Right-click the certificate, export it (in p12 mode), and enter the password. Remember this password.

Copy the file to the new computer, double-click it, and enter the password you just entered.

If it is not displayed in the organizer, double-click the mobileprovision certificate again to see the green "valid profile ". Success!

2. Delete revoke and generate it again (it is recommended that only the original revoke cannot be found)

Delete all related certificates in the key string, mainly the following: Provisioning portal,

Delete the previous items and try again, revoke. After revoke, we found that we were back to the initial state, such as: very familiar, and back to the step of uploading the private key for the first time. Before we re-create the certificate, check whether the issued certificate under the distribution label is available at this time, as shown in. Does the issued certificate still exist, indicating that it can be used: continue to check whether the devices in the devices column exist: Continue to check whether provisioning files still exist. It seems that status has changed to invalid, but the modify option is available in the future, which seems to be activated, wait for the updated version and try again: Continue to switch the provision files of the distribution label, and the status is still active. So far, it seems to be clear that the real machine debugging, you need to have the private key + (Public Key). When publishing, you can have a public key that meets the requirements? Next, let's see if the app ID still exists, as shown in: as described above, after revoke, it only has some impact on the Provision files for debugging, the rest can be used as usual, so we can recreate the certificate with confidence. We use a key string tool to generate a local private key (certificatesigningrequest. certsigningrequest). After you click request certificate on the webpage to upload the request, Apple verifies the identity of our developers and signs the generated (Private + Public) Development Certificate, repeat the created tutorial.

Double-click the newly created ios_development.cer and then open xocde-organizer. You will find that provisioning files can be used (remember to download it after modify on the website)