Renew Your Apple Developers Certificate

Categories IPADPosted on

Renew Your Apple Developers Certificate

Among the facets of developing iPad applications that may have a developer who pulls teeth is getting set up to do proper code registering for compiling applications and transferring them into the iPad for testing. And as if doing this once is not sufficient, the horror grows when it is time to renew the developer’s certification.

The Way to Develop iPad Apps

Sadly, Apple does not warn you when your certification expires, so the first thing you’re hit with is an error telling you that your iPad does not possess an appropriate profile installed on it. This will throw you over the loop since the profile itself might not have died, but in the event, the certification it’s linked to is expired, the profile will probably stop working.

Figuring out that it’s the developer’s certification that’s expired is half of the battle. The other half is getting a brand new one set up and attached to your own profiles.
Here are the steps you will have to take to get everything set up and working properly again:

Inspection: Corona SDK for iPhone and iPad Development
  1. Ask a certification that is new. You do that in the Keychain Access application, which you may find by going into your Mac’s Applications and clicking on the Utility folder.
  2. Inside of the Keychain Access, you’ll see the certificates. The certificates necessary for development is going to be named something like an iPhone Developer. They’ll also have a red circle with an X in the midst designating that they’ve expired. You are going to want to delete the certificates otherwise you may run into issues code registering your applications.
  3. As soon as you’ve cleared your expired certificates, you have to create a file asking a new one. Do this by going into Keychain Access -> Certificate Assistant -> Ask a Certificate from a certificate authority.
  4. Enter a valid e-mail address, your name and select Saved to disk from the options. Click to continue to save the document.
  5. Go into the Certificates section of the iOS Provisioning Portal to upload the document and receive a valid certification. Once you have uploaded it, then you’ll have to wait a few minutes and refresh the screen for it to be issued. Hold off on downloading the certification for the time being.
  6. Opt for the Distribution tab in the Certificates section and go throughout the exact same process to ensure you have a certification to disperse applications as well. Hold off on downloading the certification for the time being.
  7. Go to the Provisioning segment of the iOS Provisioning Portal.
  8. Select Modify and edit for the profile you would like to use to code signal your apps.
  9. From the Modify screen, make sure there’s a checkmark next to your new certification and submit the modifications.
  10. Click the Distribution tab and then go throughout the same process with your distribution profile. Hold off when loading these profiles.
  11. Launch the iPhone Configuration Utility.
  12. Proceed on the Provisioning Profiles screen in the iPhone Configuration Utility and remove your current provisioning profile and your distribution profile if they’ve not expired. You would like to replace them with your profiles connected to the certification that is new.
  13. Given that we’ve your Mac’s codesigning certification and profiles deleted, we may start downloading the new versions.
  14. Go back to the Provisioning section and download both your provisioning profile and your distribution profile.
  15. Once downloaded, you should just have double click on the files to install them from the configuration utility.
  16. Go back to the Certificates section and download the new certificates for development and distribution. Again, simply double-clicking on the files ought to be sufficient to install them in the Keychain Access.

nd that’s it. You need to be prepared to install test programs on the iPad again and again correctly submit them to the Apple App Store. A part of those measures is cleaning up the old files to make sure Xcode or your 3rd party development platform doesn’t confuse the old files with the new files. This avoids a significant headache when troubleshooting problems with the process.


Leave a Reply

Your email address will not be published. Required fields are marked *