Forum Discussion
How to Handle Delisted Apps in Google EMM During or After Device Provisioning?
Thank you for your response jeremy !
I understand that we should verify app availability before adding it to the device policy. However, suppose there are 20 packages in the Google device policy that we want to install on a device during provisioning. Does this mean we need to call the Products: get API 20 times—once for each package—to check if it’s still available before calling the Devices: update API?
This approach seems inefficient, especially at scale. Is there a more optimized way to handle this scenario? Any best practices or alternative recommendations would be greatly appreciated.
Thanks!
It’s not an issue to push a policy with package name that are not on the play store. So you could check every day or every week if those 20 packages are still available. But at the end pushing a policy with unavailable package is not an issue.
Yeah, we see the same through our MDM, the relvant app(s) are just not provided anymore.
