In this section: |
You must provide the build components. They provide absolute identification of your app name and company, and enable your customer-branded Mobile Faves app to bear this information for your end users.
Apple has extensive documentation for setting up your environment locally. The best approach to ensure that you can build an iOS application to your iOS device, such as a Mac, locally, is to be sure that both your certificate and your provisioning profile are set up correctly for code signing.
How to: |
Once you have your environment properly configured, you can export the certificate for use in your branded build. The certificate export must include the private key that was used to request the certificate.
Note: The certificate is linked to a private key.
Note: You may be asked for the administrator password of the Mac computer at this stage (possibly twice, as there are two files to export), if you do, enter the password and click OK.
You should now have a .p12 file, in your chosen location, on your hard drive.
How to: |
The provisioning profile needs to be an exact match to the APP ID that you supplied while creating the developer certificate. You can download the profile from the iOS Provisioning Portal.
Description |
File Name |
---|---|
Developer certificate. Contains your signed and verified company and app identity information for builds. |
distribution_identity.p12 |
Application provisioning profile. Directs the build system on how to stamp your application with your Apple-approved app ID. This enables confirmation of your app for installation on iOS devices. |
Team_Provisioning_Profile_.mobileprovision |
The iOS Provisioning Profiles window opens, as shown in the following image.
The App ID that you provide must match the one that is highlighted in the following images.
|
WebFOCUS |