User Tools

Site Tools



Provisioning and signing is the act of preparing both devices to receive a project, and projects to deploy to a device.

Its a painful process the first time. There are varying tiers of deployment.

Installing on a device to test is the simplest, and requires plugging in a compatible device, finding it in Window > Organized, and selecting “Use for Development.” The device can then be selected as a target to the right of the play button, installing the app on the device for 30 days. This is known as provisioning.

Deploying the app to the App Store or testers is more involved. You must have an apple developer account (100$ a year; UW Madison has an educational account that allows up to 100 devices to be provisioned.)

Each account gives you a keypair and the ability to create provisioning profiles. The keypair is a public and private key used to cryptographically sign your profiles and applications, and ensure that only valid holders of your keys can use your applications, as well as uniquely identifying you. A provisioning profile is a list of devices that are allowed to run an application with a given name, signed by your private key. It must be distributed with applications that are released for testing or to the store and is used in the process of installing the application.

The requirements to deploy to tester devices:

  1. Relevant devices must have their UDID (unique device identifier) added under the development account
  2. Account holder must generate profiles with a given project name (bundle identifier) and download them
  3. Developer must compile the project into an archive from xcode using the private key
  4. Developer distributes the archive, public key, and provisioning profile to testers or to App Store

The above is a broad outline; you will have to research the topic or ask your TA for help if you plan on installing on a device.

ios-labs-s14/intermediate-prov.txt · Last modified: 2014/02/23 22:52 by mbarboi