Menu
So I'm using the Android Management API to manage and handle deployment for an app to a kiosk device I am working on.
I've created an organisation, created a policy, and ensured the app is limited to managed google play only, and assigned the organisation to the app.
I've enrolled some devices onto the policy, and when the app is moved to prod (currently this is fine as there are only a handful of test devices on that policy), it downloads and installs.
However my issue is that if I use the alpha track, and then assign the organisation to that alpha track, the new alpha version of the app never gets installed.
Using the opt-in URL (not ideal, as the policy doesn't have Chrome on it, so I would need to specifically add chrome just for alpha testing), then sign into google with an account on that organisation. It then tells me I am enrolled into alpha, and it may take a few hours for the app to show up.
The google docs on this are extremely vague
If your app is private, you also need to add the organisation associated with your test to your targeted list.
Like 16 hours later, no app, only the prod version which comes pre installed. If I call that device from the Android Management API, and show installed apps, it shows only the prod / previous version of the app.
So my question: How do I get the app onto the device via the alpha test channel, while using a private app + organisation?
466
Go to Release > Setup > Advanced settings. Select the Managed Google Play tab. In Organizations, click Add organization. For each organization that you want to publish the app to, enter the Organization ID and a description (or name) and click Add.
Distribute your app to testersSelect your Firebase project when prompted. On the Releases page, select the app you want to distribute from the drop-down menu. Drag your app's APK file to the console to upload it. When the upload completes, specify the tester groups and individual testers you want to receive the build.
To publish private apps from the Play Console, you need to register for a Google Play developer account. The account gives you the correct administrator privileges to upload and publish private apps to managed Google Play. You can then use your EMM console to distribute these apps to users.
If you don't want to release your app on a marketplace such as Google Play, you can make it available for direct download to your users (sideloading). Export the APK file of your application and provide users with the download link. Users must opt-in for installing unknown apps.
Update 2019-09-09
The Android Management API now supports distributing testing tracks:
Initial answer 2019-03-14
The Android Management API doesn't support distributing testing tracks at the moment. We are working on adding support for it, however I cannot share a precise timeline at the moment.
Once support is added you will be able to set a field in the ApplicationPolicy to distribute testing track of an app to a device. Similar to how it is currently possible using the Play EMM API (see documentation).
Unfortunately there is no workaround. Using the opt-in URL from the device would not work with the Android Management API. And you cannot use the Play EMM API for devices managed with the Android Management API.
158
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
