Skip to end of metadata
Go to start of metadata

To distribute an iOS application—including the native iOS App Catalog—to your App Catalog users' devices, you must first prepare it for distribution. The end result is an iOS app that is "signed" and authorized for distribution. Signing (also known as "code signing") is the process by which an iOS app is sealed and identified as yours. An unsigned app cannot run on an iOS device. EASE provides a signing server that lets you sign apps directly through the EASE Portal. EASE also provides an option for downloading a signing package to sign an app outside of EASE. For more information on using the signing server or downloading a signing package, see Signing Applications.

To sign an iOS app using either the EASE signing server or the signing package, you need a valid Apple distribution certificate (also referred to as a "production certificate") and distribution provisioning profile. To enable an iOS App Catalog for push notifications, you also need a production push SSL certificate. The following diagram illustrates the main task flow for creating these components. For more information, click on the tasks listed to the right of the diagram. Before performing any of the tasks, review General Requirements to check that you have everything you need.

This topic is for quick reference only. For more detailed information on preparing iOS apps for distribution, see Apple's iOS Developer Library.

 

  • No labels