A requirement to create an iPad app
Follow the steps below to create a provisioning profile
Apple built a security model for iOS that requires a combination of a security certificate and a private key in order to 'codesign' apps and be able to either install them on an iPad outside of the App Store, or to submit them for review in the App Store.
Below we are describing the steps required to create your own provisioning profiles. More detailed documentation about provisioning profiles is available from Apple's developer portal.
Login to Apple's Developer Member Center, then select "Certificates, Identifiers & Profiles".
Click the "How To" tab to get information on how to generate a certificate signing request and download an iOS Distribution Certificate. Although the "How To" may describe the procedure for obtaining a Development Certificate, it is exactly the same for obtaining a Distribution Certificate.
At the end of this procedure, you will need to have downloaded and installed a Distribution Certificate. A Distribution Certificate identifies your development team. When it’s stored in your keychain, it includes the team’s private key.
Twixl Publisher uses Development Certificate and Development provisioning profiles for testing purposes, and a Distribution Certificate and Distribution provisioning profile for Ad Hoc and App Store distribution.
IMPORTANT NOTE FOR TEAMS:
If the certificate has already been created (e.g. by a colleague), then the easiest procedure is to ask that colleague to export the combination of the distribution certificate and the private key using the Keychain Access application. Exporting those 2 items will generate a file with extension .p12 - open this on your own computer to add them via the Keychain Access application. Alternatively, it is also possible to select "Export Developer Identity" from the Tools menu in the Twixl Publisher app.
Now you need to assign the devices you want to use for your Ad Hoc builds.
Locate the Unique device ID in iTunes (click on "Serial Number" and the Identifier will be displayed - copy the UDID via cmd-C). Now add the UDID(s) to the 'Devices' section of the iOS Provisioning Portal. You'll find more information about this via the "How To" tab.
Adding these devices is only required for creating "Ad Hoc" test builds for internal use.
An App ID consists of a universally unique 10 character "Bundle Seed ID" prefix generated by Apple and a "Bundle Identifier".
The recommended practice is to use a reverse-domain name style string for the "Bundle Identifier" portion of the App ID, e.g. com.yourdomain.yourpublication.
Again, you'll find more information in the "How To" tab.
You should not use a wildcard app ID (i.e. an asterisk) for your application.
In order to build your application for Ad Hoc distribution, you will need to create and download an Ad Hoc Distribution Provisioning Profile.
Follow Apple's instructions via the "How To" tab of the "Provisioning" menu. Although the "How to" describes the procedure for creating Development Provisioning Profiles, it is exactly the same for creating a Distribution Provisioning Profile.
Keep the provisioning profile you just created at hand. You will need it during the 'build' process.
Once you have gone through the process of generating an "Ad Hoc" provisioning profile, you'll also be able to follow the same procedure to create an "App Store" provisioning profile. You will need this profile when you are ready to create a build of your app to submit to the App Store.