|
Building an iOS app for Development Test and AdHoc Distribution
|
| |
| What is the difference between building an app for Development Test or for AdHoc Distribution?
|
| Apps built for Development Test are generally built for debugging by one or more developers on one device, or a small number of devices.
|
| Apps built for AdHoc Distribution are typically built for use by one or more end-users (or "Beta testers") and typically run
on more devices (up to 100, or more under the iOS Developer Enterprise Program).
|
|
In both cases, apps may be downloaded directly from a mobile device using the Safari web browser by accessing an internet URL. This is called "over-the-air" or OTA installation.
|
| What are the steps for building an iOS app for Development Test using Appception?
|
| To build an iOS app for Development Test using Appception, a Development Certificate (in .p12 format), and a Test provisioning profile (.mobileprovision) are required.
|
| A Development Certificate (in .cer format) and a Test provisioning profile (.mobileprovision) may be obtained using the iOS Developer Portal, iOS Dev Center, and the iOS Provisioning Portal.
|
| Then, the Development Certificate (in .cer format) must be converted to a Development Certificate (in .p12 format); this conversion is described in the FAQ. The .p12 format includes both the Development Certificate and a private key; it may be used to sign an app.
|
| Next, the Development Certificate (in .p12 format) and the Test provisioning profile (.mobileprovision) must be uploaded
to the 'ios/build/debug' folder of the app. See the Projects
tutorial for more information about uploading files.
|
| Then, the app should be built for Debug.
|
| Note that the password used to generate the Distribution Certificate (.p12) must be entered to build.
|
| What are the steps for building an iOS app for AdHoc Distribution ("Beta test") using Appception?
|
| To build an app for AdHoc Distribution using Appception, a Distribution Certificate (in .p12 format), and an AdHoc provisioning profile (.mobileprovision) are required.
|
| A Distribution Certificate (in .cer format) and an AdHoc provisioning profile (.mobileprovision) may be obtained using the iOS Developer Portal, iOS Dev Center, and the iOS Provisioning Portal.
|
| Then, the Distribution Certificate (in .cer format) must be converted to a Distribution Certificate (in .p12 format); this conversion is described in the FAQ. The .p12 format includes both the Distribution Certificate and a private key; it may be used to sign an app.
|
| Next, the Distribution Certificate (in .p12 format) and the AdHoc provisioning profile (.mobileprovision) must be uploaded
to the 'ios/build/release' folder of the app. See the Projects
tutorial for more information about uploading files.
|
| Then, the app should be built for Release.
|
| Note that the password used to generate the Distribution Certificate (.p12) must be entered to build.
|
|
Note: iOS apps may also be built for Release to the iOS App Store.
|
| |
|
Questions? Contact us
|
|
|