Work profile
Fully managed
App management

Change log

Support this site

Share this page

How to resolve common Android app install failures (with errors)

Looking to understand some of the most common application installation errors? I've compiled a list below.

For clarity, these messages are provided by Android, with the exception of ENTERPRISE_AUTO_INSTALL_ERROR_NOT_COMPATIBLE_WITH_DEVICE, which is received via CloudDPC/Google Play during the automatic installation process. The scenarios therefore when these messages would show in logs is when an application is locally installed directly on the device, via -

On-device app installation errors

There's an identical version of the application you're trying to install already present on the device. Have you updated your version code? If not, and you don't want to, remove the existing application first.
Android considers the package to be invalid. It may be corrupt or not packaged correctly.
There is no space remaining on the device. Delete all the saved memes and try again.
Though the application itself may be unique, it shares a package name with an app already installed. Update the package name, or remove any existing duplicate-named packages from the device first.
Android tried to update an existing installed application with the new one being presented, but the signatures don't match. Double-check the signing keys used. If this is an intentional change, you'll need to first remove the old application from the device.
Installation may have worked, but the application failed to validate its DEX files. There may not be enough space, or an application issue is present.
The minTargetSDK of the application is higher than that of the device. For example, trying to install an application targeting Android 14 (API level 34), on a device running Android 12 (API level 31). Note this is explicitly minTargetSDK, which defines the minimum version of Android an application will run on. This can be due to a particular library in use relying on newer functionality, or a misconfiguration.
The application is flagged as a test app. Build for debug or release instead.
The application likely isn't compatible with the device architecture, but there are a few nuances to ABIs and the appropriate debugging should be undertaken.
The application defines required features in the app manifest that aren't present on the device. For example telephony, camera, GPS, etc. See ENTERPRISE_AUTO_INSTALL_ERROR_NOT_COMPATIBLE_WITH_DEVICE below for further details and resolution.
The installation verification process timed out or failed. Retry the installation.
If it continues to time out, or verification repeatedly fails, Google Play Protect is unhappy with the application. You may disable verification via ADB:
adb shell settings put global verifier_verify_adb_installs 0
Or through device Settings > Developer settings > Verify apps over USB
The application being installed is of a lower version code than that already present on the device. The existing installed application would need to be removed because Android doesn't support rolling back.
Be honest, you're trying to bypass the permission model introduced in Android 6.0 with an update, aren't you? You can't do this. Any new version of an app that targets an SDK version supporting the runtime permissions model can only be updated with a version that still supports runtime permissions. You could remove the old version and install the new version fresh, though you really should just support runtime permissions.
A restriction on the minTargetSDK version introduced in Android 14. Target a newer SDK version for these devices. Read more here.
Android only supports .APK files when not directly installed from a Store. If you're trying to sideload a .AAB, convert/build to .APK and try again.
Your AndroidManifest.xml file is missing or corrupt. The application source will need to be reviewed, and a new build repackaged for installation.
Your AndroidManifest.xml file has a missing or incorrectly formatted package name. The application source will need to be reviewed, and a new build repackaged for installation.
Android fell over. Try again?
Android fell over in a different way. Try again?
Android continues to fall over, but do check the integrity of the application since this is a parser error, though the reasoning is not provided for the installation failure.
The user associated with the installation request is not permitted to install applications. Review policies or attempt to install under an alternative user.
This happens when there is an issue detected with the application signature. Validate the app signing process and try again.

Cloud/agent-derived installation errors

This often happens when the Play Store determines an app is not compatible with the device it has been assigned to. Commonly this is permission or - more specifically - feature related. The specific features requested (either explicitly with uses-feature or automatically through assumed feature requirement if only uses-permission is declared without uses-feature), are not available on the hardware.
Review the permissions/features in use, and if you'd like to use a permission without mandating the associated feature be present, declare android:required="false" explicitly per-permission that isn't critical to functionality.

Missing anything?


Raise an issue, or get in touch.

mail Reply by email | edit_note Edit this page.


Work profile
Fully managed
App management