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

Android > Troubleshooting

Troubleshooting Android application deployment

Updated on December 7th, 2023

This article will provide information regarding the most common troubleshooting cases when it comes to Android application deployment. At times installing applications on an Android device might fail or get stuck into the status "In progress". Or it might appear that the application installation is successful even if the device is not updated. There are a few general issues you can check first if you meet problems with Android application deployment.

Failed 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 to the device and therefore the managed Google account does not exist. A managed Google account is required for the deployment of the managed Google Play applications.
  • Make sure you have the user selected when you are implementing the Managed Google Play creation action. It needs to be selected in order for the action to go to the completed state as seen in the below screen capture. See the instruction video for further information.
    Managed Google Play account creation completed. The row highlighted in yellow.
  • Account creation request is shown on your device as seen in the screen capture below. The user needs to press the notification on the device before the Managed Google Play account creation starts and completes.
    Miradore managed account creation request pop up on the device.
  • Screen capture showing the creation of the Managed Google Play Account below. Please be patient.
    Miradore app creating a Managed Google Play Account.
  • There are updates on the application permissions, and you need to approve them. It is recommended to set up auto-updates in Play Store App (Menu > Settings > General > Network preferences > various auto-update related settings to adjust.) For further information please see How to update the Play Store & apps on Android article.
  • The application is country restricted and the device location is wrong. See more information here.

When the application deployment seems to get stuck:

  • Make sure that adequate space is available for the application(s) to install. To see tips about how the free up space see the Android Help article.
  • Check that the device has proper network connectivity. Sometimes, rebooting the WiFi device is needed. Sometimes just a simple reset might not work and you need to make sure to wait for 30 seconds once you've turned off the router for it to completely restart and re-establish itself.
  • A slow Internet connection might be the cause of the process taking longer than expected. If the connection is not good enough it might cause the app not to download, to begin with. To check the speed of your connection you can use a site such as Speedtest to get an up to date information about the connection.
  • Please see Network insights for Wi-Fi devices for further information.
  • It has come to our attention that in some rare cases application deployment from business policies are not showing on the devices. Manually deploying another application from Managed Google Play Store can kickstart the business policy application deployment.

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.
  • You can try to retry the deployments using the Retry link on the Device page's Action log (Management > Devices > Device).

Retry application deployment under the device action log.

  • 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 on 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 that prevents device users from removing the managed account? See Prevent device user from removing the managed Google Play account from a managed Android device.
  • Try to remove and re-create the managed Google Play account for the device(s). You can do this from the Device page using the Managed Google Play > Remove managed Google Play account and Create account/work profile menu actions.

Recreating the managed Google Play account usually helps if you are getting the "Installation failed with error 'Failed to get the device from EMM API with error 'not found: No device was found for the given id.'"

  • Sometimes the terms and conditions of the Play Store or the application might change. Accept the terms and conditions, if needed.
  • When a 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 Google Play updates. 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.


Please see Installing Miradore Client from APK article for step-by-step instructions.

  • Check the settings of the APK from Miradore (Applications > Application > Application version - Deployment settings). If deployment over the metered network is not allowed, the application deployment status is In progress in Miradore until the device has WiFi access for the application installation.
  • 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 the 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 [email protected].

Known issues

Installing applications that target SDK23 (Android 6), or lower versions, is not supported on Android 14 devices.

Previous Article:

Next Article: