Your iPhone app on your device

This is from memory so may contain a few jumps of logic, but I needed to write a quick tutorial for getting code on the iPhone for my Kliq cofounder and figured that it may be useful for the internet-at-large. It assumes you already have working code in the iPhone simulator that you simply want to push to an iPhone (or iPod, iPad, etc.), and moreover, that you can fill in the blanks as this is written as a basic sketch of what needs to be done not a detailed step-by-step handholding. If you are working in a team, some of the steps may already have been done for you, so obviously just goto the first uncompleted step.

  1. Get an iPhone developer account. The rest of this is done from
  2. Go to Provisioning portal->Certificates. Download the WWDR intermediate certificate. Create a new development certificate by opening Keychain Access on your machine, then going to Certificate Assistant->Request a Certificate from A Certificate Authority. Fill out the info, and save to disk. Then upload the saved file to the developer connection.
  3. Go to Provisioning portal->Devices->Add Devices. Enter a name for your device, and a device ID, which can be found via iTunes or XCode->Organizer.
  4. Go to Provisioning portal->App IDs->New App ID, fill out the relevant info noting that the Bundle Identifier (App ID Suffix) will need to be entered, or identical to app ID suffix in your existing application, as defined in its Info.plist file.
  5. Go to Provisioning portal->New profile (Under the Development tab, I’ll make another post for the Distribution steps when we at Kliq are ready for that). Select your device and the app ID created. Submit, hit reload, and download your new provisioning profile.
  6. Almost there! Open up your project in XCode, change the active SDK to your device, and click Build and Run. You should be prompted for the password of the keychain on which the certificates lie and then see your application build successfully and launch on your device

Problems? The error space on this chain of events is huge,  as XCode is twitchy and particular, but usually issues can be resolved by googling the error and playing around with suggestions from the web. I’ll be making a post with common code signing issues soon.

Leave a Reply

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