Skip navigation

Criselda Flores Abarquez' Blog

January 18, 2020 Previous day Next day

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”.


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


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


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


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


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


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.


Manage app updates - Managed Google Play Help


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

Part 2 of 3

Part 1

Part 3

B. Add a New App Version

The steps below outlines steps to publishing apps to the alpha or beta testing tracks in Google Play console, then assigning those to Workspace ONE UEM smartgroups.

1. Login to the Workspace ONE UEM console

2. Go to Apps & Books\ Applications\ Native\ Public\ Click “Add Application”

3. Select Platform: Android. Name can be kept blank. Click “Next”

4. Select the private apps icon on the left.



5. Click “Make advanced edits” under Advanced editing options. This will take you to the Google Play console login page.


6. After logging in to the Google Play console using the google account tied to your Workspace ONE tenant, go to your app and navigate to Release management\ App release. You can select alpha or beta track. In this example, we will add an apk to the Alpha track. Click “Manage” in Alpha track.


7. In organizations, click “Edit”


8. Check the organization corresponding to the Workspace ONE organization group. Click “Done”.


9. Click “Edit Release”


10. Add the apk file. After adding the apk, you will see details about the version code and size of the file.


11. Click “Save” at the bottom of the page, then “Review”.


12. View any of the warning messages and make changes to the app, as necessary.



13. Click “Start Rollout”, then “Confirm” at the pop-up window.


14. In UEM console, select the app under Apps & Books\ Native\ Click “Assign”


15. Click “Add Assignment”


16. Select the Assignment Group who you want to get the new version (alpha) of the app. Enable Managed Access, select Alpha as Pre-release version. Click “Add”.


17. In the verification screen move up priority of your group where the pre-release is assigned.


18. Then click “Save and Publish”


19. Click “Publish” to confirm the assignment. This will make the alpha version of the app available to the devices belonging to the smart group chosen in Step 16.


Note: Same process can be done for Beta release


(continues to Part 3)

Part 1 of 3

Part 2

Part 3


This step-by-step guide shows how to upload internal apps (apks you’ve developed) to the Android Managed Play Store for your organization via Workspace ONE. Subsequent sections also show how to add other versions for Alpha/ Beta testing in the Google Play console, then manage assignment of those versions to specific devices/ users in Workspace ONE.



  1. Workspace ONE environment already registered to Android EMM


  2. Apk file with an application ID that has not been published in the Android public play store.


A. Publish a New Application

1. Login to the Workspace ONE UEM console.

2. Go to Apps & Books\ Applications\ Native\ Public\ Click “Add Application”.

3. Select Platform: Android. Name can be kept blank. Click “Next”.


4. Select the private apps icon on the left.


5. Click the “+” button to add a new app.


6. Make sure to add a Name, then select “Upload APK”.


The “Create” button will be enabled if the app can be uploaded.


7. You will see the app in the Private apps section, and a notification that publishing in your store may take up to 10 minutes.


8. Close this screen. The app you just uploaded will be the app list under Public apps.


(Optional) To edit the logo shown in the console, click on the pencil icon beside the app.  Note that this only updates the icon in UEM, not in the Play store.



9. Save and assign the app.


10. Click Add Assignment


11. Pick the organization group/ smart group you would like to assign the app to. Click add.


12. Update Assignment pop-up will appear. Click “Save and Publish” to confirm. Then “Publish” at the Preview Assigned Devices page.



13. You will return to the app list screen. If the deployment is set to “Automatic”, app will get installed automatically on the device and show in both the Workspace ONE Hub/ Catalog and the  Google Play Store.




(continues to Part 2)