barscaret-downcaret-leftcaret-rightcaret-upcheckchevron-leftchevron-rightfile-pdfinfosign-in-altsignin text-widthtimesyoutube

Android > Troubleshooting

Troubleshooting Android Application Deployment

Updated on May 4th, 2021

Sometimes, installing applications on an Android device might fail or get stuck into the status "In progress". Or it seems that the application installation is successful even the device is not updated. There are few general issues you can check first if you meet problems with application deployment.

If the application deployment fails, go to the Miradore Action log view and check the status details of the application deployment. Some possible reasons for the failure:

  • There is no user assigned for the device and therefore the managed Google account does not exist. The managed Google account is required for the deployment of the managed Google Play applications.
  • The application has updated permissions, which need to be approved.
  • Application is country restricted and the device location is wrong. See more information from here.

When the application deployment seems to get stuck:

  • Make sure that adequate space is available for the application(s) to install.
  • Check that the device has proper network connectivity. Sometimes, rebooting the WiFi device is needed.

If these device-related things are fine, you may still consider some aspects.

Managed Google Play applications

  • One of the most common reasons for deployment issues is that the application is already on the device. This is possible, especially, if the option "Keep system applications" is chosen during device enrollment. In this case, application deployment is not able to turn the existing application into a managed application. Try to remove the installed application manually.
  • If the managed account is missing from the device, application deployments usually get stuck in "Queued" status. Google services framework ID field is usually empty at the Device page in Miradore if there is no managed account on the device. Did you know that it is possible to create a configuration profile which prevents device user from removing the managed account? See Prevent device user from removing the managed Google Play account from a managed Android device.
  • Sometimes the terms and conditions of the Play Store or the application might change. Accept the terms and conditions, if needed.
  • When data saver is enabled on the device, ensure that Google Play Store and Google Play Services are excluded.
  • Check that you have installed all pending updates from the Play Store. Sometimes, a missing Android System Webview update may block app deployments.
  • The actual application installation process is done between Google and the device. If there is a delay, it is usually on the site of Google and at the moment there is no tool in Miradore to monitor this connection.

APK

  • Verify that there are no issues with the APK file by installing the application manually on the device. You can do this via a USB connection, with the APK used in Miradore application deployment. In some cases during the manual installation, you might receive an error message giving you some more information about the problem.

When you try to update the application, the deployment might sometimes appear as "Completed" in Miradore although nothing seems to happen at the device.

  • Make sure that the developer of the in-house app has updated the application version (setting VersionCode) of the app wrapped within the new APK file. After verifying the version is correct, try to update the application again.

Play Store application

  • The user has not accepted the installation request on the device.

 

If the issue still exists after troubleshooting, please contact Miradore support support.online@miradore.com.

  • This field is for validation purposes and should be left unchanged.

Next Article:
»