Hor*_*rse 8 android google-play android-testing android-enterprise android-management-api
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
如果您的应用程序是私有的,则还需要将与测试关联的组织添加到目标列表。
像16小时后一样,没有应用程序,只有预装的产品版本。如果我从Android Management API调用该设备,并显示已安装的应用程序,则该应用程序仅显示该产品的产品/以前的版本。
所以我的问题是:如何在使用私人应用程序+组织的同时通过alpha测试通道将应用程序添加到设备上?
更新2019-09-09
Android Management API 现在支持分发测试轨道:
初步答复 2019-03-14
Android Management API 目前不支持分发测试轨道。我们正在努力增加对其的支持,但目前我无法分享准确的时间表。
添加支持后,您将能够在“ApplicationPolicy
将应用程序的测试跟踪分发到设备”中设置一个字段。与当前使用 Play EMM API 的方式类似(请参阅文档)。
不幸的是没有解决方法。使用设备中的选择加入 URL 不适用于 Android Management API。并且您无法将 Play EMM API 用于通过 Android Management API 管理的设备。
归档时间: |
|
查看次数: |
271 次 |
最近记录: |