Here's how to troubleshoot problems you might have with the managed Google Play store. For complete information on using Google Play in your organization, see the Managed Google Play Help Center.
I have pushed an application to my profile, but it does not install on my devices
- Verify that the application has the install type "Force Installed"
- Verify that the policy "Disallow install applications" is disabled
- Verify that the application is compatible with your devices
- If in kiosk mode: verify that you have correctly added the application package name to the configuration of the Kiosk launcher.
- If the app is a self-hosted private app: check that you are connected to the correct network. If your organization hosts the APK for this app themselves and only allows downloads from a server accessible on the organization's network or VPN, then the user must connect to the organization's network to install the private app.
If these steps fail, gather as many screenshots, videos as possible, then collect a bug report immediately after your device has received the WizyEMM profile, and send these elements to us at email@example.com
My application does not update on my devices
The application update I have successfully uploaded to WizyEMM through Google Play does not install on my devices.
Verify that you have correctly implemented your update policies on your WizyEMM profile. You can choose between 3 update policies : set network constraints, set a maintenance window, & set a minimum version code. Read more on this article : Manage app updates.
- Even if you have set network constraints, your application will only update if:
- The device is charging.
- The device is idle (i.e. not actively used).
- The app to be updated is not running in the foreground.
- If you have set a maintenance window, your update policy will dismiss the previous 3 constraints during the maintenance window. It can take up to 24 hours for an app update to be added to the update queue. After an app is added to the queue, it will be updated automatically the next time the device is in the maintenance window if the network constraint is met. As a result, it can take up to 48 hours for an app to update after you set a maintenance window.
- Setting a minimum version code overrides default update behaviors and interrupts the on-device experience for users. This method is therefore intended for critical updates only.
If apps aren’t updating automatically on the devices you manage after following the best practices in this article, we recommend sending us a bug report:
- In your WizyEMM console, set the maintenance window to a narrow range (for example, 30 minutes).
- Allow a device to enter idle state for longer than the maintenance window specified in step 1.
- Be sure you have Developer Options enabled.
- Install adb on your computer (read ou article on how to generate an Android bug report for more information)
- Connect the device to your computer and agree to allow USB debugging if prompted.
- At the terminal enter the command in the code snippet below, then collect a bug report and send it to us at firstname.lastname@example.org for inspection.
adb logcat -G 32M; adb shell setprop persist.log.tag.dpcsupport VERBOSE; adb shell setprop persist.log.tag.Finsky VERBOSE; adb shell setprop persist.log.tag.Auth VERBOSE; adb shell setprop persist.log.tag.PackageManager VERBOSE; adb shell setprop persist.log.tag.JobScheduler VERBOSE