Ensure that you can successfully generate an installation package with a signed iOS app by creating an iOS certificate set. With a certificate set, you provide components that control how you distribute your app to users and that determine what services are available. For example, you can create a certificate set that enables support for features such as push notifications.

Before you begin: Obtain the components to use in the iOS certificate set:

• App ID

  For more information, see Obtaining an App ID for iOS apps.

• Signing certificate

  For more information, see Obtaining a signing certificate for iOS apps.

• Mobile provisioning profile

  For more information, see Obtaining a mobile provisioning profile for iOS apps.

• Push notification certificate (for apps with push notification support)

  For more information, see Configuring push notifications for iOS apps.

1. In the navigation pane of App Studio, click SettingsMobile certificates.
2. On the Mobile certificates page, click Add certificate set.
3. On the Adding new certificate set page, click iOS.
4. Choose a mobile provisioning profile to use in the certificate set:

   Choices	Actions
   Use an existing provisioning profile	In the Mobile provisioning file list, select an already uploaded profile.
   Upload a new provisioning profile	Next to the Mobile provisioning file list, click New. In the Upload new mobile provisioning file modal dialog box, click Choose file, and then upload the .mobileprovision file. In the Profile name field, enter a name for the provisioning profile. The name must not include underscore ( _ ), hyphen ( - ), or period ( . ) characters. Click OK.

5. If the provisioning profile that you use has a wildcard App ID, in the App ID (Bundle ID) field, enter a unique bundle identifier for the iOS app.
6. On the Adding new certificate set page, choose a signing certificate to use in the certificate set:

   Choices	Actions
   Use an existing signing certificate	In the Signing certificate list, select an already uploaded certificate.
   Upload a new signing certificate	Next to the Signing certificate list, click New. In the Upload new certificate file modal dialog box, click Choose file, and then upload the .p12 file with the signing certificate. In the Certificate name field, enter a name for the signing certificate. The name must not include underscore ( _ ), hyphen ( - ), or period ( . ) characters. In the Encryption password field, enter the encryption password for the certificate. Click OK.

7. Optional: To enable push notifications for your app, on the Adding new certificate set page, choose a push notification certificate to use in the certificate set:

   Choices	Actions
   Use an existing push notification certificate	In the Push notification certificate list, select an already uploaded certificate.
   Upload a new push notification certificate	Next to the Push notification certificate list, click New. In the Upload new certificate file modal dialog box, click Choose file, and then upload the .p12 file with the push notification certificate. In the Certificate name field, enter a name for the signing certificate. The name must not include underscore ( _ ), hyphen ( - ), or period ( . ) characters. In the Encryption password field, enter the encryption password for the certificate. Click OK.

   Note: The mobile provisioning file that you use in the certificate set must support push notifications. Otherwise, the push notification certificate area is not available.
8. Click Save.

Result: You now have a complete certificate set that you can use to generate an installation package for your app for testing or distribution, and ensure that the app is signed and meets Apple requirements.

For example: A mobile app developer for the uPlus company creates a certificate set for the iOS expense reporting app.

What to do next: Generate an installation package for your signed iOS app. For more information, see Building mobile apps.

• Creating an unsigned iOS certificate set

  Create an unsigned iOS certificate set to generate a mobile app bundle as an unsigned xcarchive file. You generate an unsigned bundle to sign it locally with Xcode on a macOS computer when your company policies do not allow you to upload mobile certificates and provisioning profiles to third-party tools.