Publishing an app release

After the app release is successfully re-signed, it can be published to the assigned app store or EMM system. Before attempting to publish an app release, be aware of the following conditions:

Table 8.  Conditions for publishing an app release

App Store	Situation	Condition
Google Play	Initial release	You cannot upload the initial release. You need to create the initial release through the Google Play console. All subsequent releases can be published automatically using Ivanti incapptic Connect.
Google Play	Publishing	The new release is published to the public after it is uploaded to Google Play through Ivanti incapptic Connect. There is no way to directly upload it to Google Play and publish it later.
Google Play Apple App Store	App rejections	Due to API limitations, Ivanti incapptic Connect does not automatically show the detailed information about a rejection. Instead, after you receive the rejection email, you can reject the release and state the reason.
WorkSpace ONE UEM (VMware AirWatch)	Initial release	The initial release should be assigned to the assignment group(s). For each subsequent release, the assignment group is automatically copied. As far as Organizational Groups (OGs) are concerned, Ivanti incapptic Connect uploads the binary to all OGs where a previous release was uploaded.
Ivanti	Post-publication labels	After publishing to Ivanti, you will need to assign labels. See Using Ivanti EPMM Delegated Label Management.

To publish an app:

Procedure

1. From the Ivanti incapptic Connect > Apps page, select the app with the release you want to publish.

2. Click Publish.

   If there are more than one endpoint management systems assigned to the app, there will also be multiple publishing buttons available.