High Priority mode takes 10 hours to update apps on devices

Yes, this is another example of how attempts at proper version control in Android Enterprise have fallen flat. My end customers that I manage expect to be able to install apps on their devices in specific controlled upgrade windows. Managed Google Play does not provide that level of control that is needed, even with this High Priority mode, so I prefer to use direct APK installs with Custom DPC based EMMs, and will continue to do so until proper version control is added to Managed Google Play. 

After this update completes, do you see a similar delay in the next update?

I wonder if the 10 hours is consistent across future updates, or relates to the High Priority mode being properly recognized in the Google Play client, rather than the update of the app itself.

In the meantime, as Matt mentioned above, we support Internal Apps for Fully Managed devices to provide the level of control & speed you are looking for.

Hi everyone!

I performed several app updates on devices, and many of them took around 10 hours. Therefore, the High Priority setting should already be correctly applied.

Our need is to deploy both public and private applications, although we require more agility specifically for private apps. We understand that Android Enterprise recommends using Managed Google Play, is that correct? We’re concerned about ignoring this recommendation and creating a fragmented user experience across different stores.

We also understand that this delay comes from Google’s side. We know we can reduce this waiting time by executing the WSO UEM API calls on the device (QueryDevice, SyncDevice, apps/public/install, etc.). Our actual question is whether this Google behavior is typical, whether other customers experience the same delay, and whether there are other alternatives to improve it (beyond the API already mentioned).

Thank you for your responses.