Sign Apps with the Proper Credentials
In order for push notifications and application policies to work properly with multiple iOS App Catalogs:
- Each of the iOS App Catalogs must be signed with a different provisioning profile that is associated with a unique explicit App ID. When creating the suffix for an App ID for an App Catalog, use
appnameto ensure that the domain portion of the suffix is different. For example:
com.example.prodorg.appcatalogFor instructions on creating a unique explicit App ID, see Manage App Identifiers.
- The iOS App Catalog and each of the iOS apps in the same organization must be signed with credentials created using the same Apple account so that they share the same Team Identifier (Team ID). Apple uses the Team ID for the App ID prefix of an App ID.
- The SSL push certificate uploaded with each App Catalog must also be created using that same Apple account. For instructions on creating a push certificate, see Manage SSL Certificates for Push Notifications. For instructions on uploading a push certificate to Apperian, see Push Notification for an App Catalog.
Reapply Policies and Re-sign
For app policies to work properly with multiple iOS or Android App Catalogs, all apps with policies will need a new version of the policy layer. To get the latest policy layer, you must reapply policies and re-sign each app with policies, and then deploy the new versions as mandatory updates.
If you sign the app with Apperian, do not select the Enable app option when you sign it. You should enable the app on the Edit Application page and also mark it as a mandatory update.