part 3 of 3

Part 1

Part 2

C. Release Alpha/ Beta track app to Production

1. In the Google Play console, while your app is selected, go to Release Management\ App releases. In Alpha, select “Manage”.

4-1.png

2. Select “Release to Production” at the Release section.

4-2.png

3. You will see the new release to production page.

4-3.png

Scroll to the bottom and click “Save”, then “Review”.

4-3-2.png

4. Click “Start Rollout to Production”. This will release the Alpha/Beta apk to the Production track.

4-4.png

5. The Alpha (or Beta) track will now be empty and show it was promoted to Production.

4-5.png

In UEM, all the devices that have the Prod version assigned to it will see that the update is available on the Managed Play store.

In the case where the Alpha(Beta) track is superseded, devices in the Alpha (Beta) track will get the Production version of the app.

UEM currently whitelists the track it sees the device is first assigned to in UEM (following the priority in Assignments of the app in UEM). Refer to this post for a more detailed explanation of expected behavior.

 

Note: It may take time for any new version of the app uploaded in Play console (or via Workspace ONE in iFrame) to get automatically installed on the work profile. Refer to this Google article. To manually install the available update, end-user can go to the Managed Play store and see updates available in My work apps\ Updates section.

References

https://developers.google.com/android/work/play/emm-api/distribute#distribute_apps_for_closed_testing

Manage app updates - Managed Google Play Help

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1912/Application_Management-for-Android/GUID-49EE45D2-A44A-4695-B0E5-E45BEFC8FDA9.html

 

Update Notes:

  1. v1: Jan 12, 2020
  2. v2: Updated section C with behavior after Alpha/ Beta promotion to production and app update behavior on device
  3. v3: Feb 13, 2020 - added link to new post explaining how UEM priorities work with Managed Play console tracks and versions