Cortado Support

My Tickets Visit www.cortado.com
Welcome
Login

Possible error messages when installing self-hosted Android apps

In this article you will find a list of possible error messages for errors that can occur when installing self-hosted apps. 

After installing a self-hosted app, always check whether the installation was successful. 

  • To do this, open the device management under Administration→ Devices and select the relevant device in the left-hand column.
  • Then click on Managed apps in the Apps tab. Here you will find all assigned apps, including self-hosted apps. 
  • Under Status, you can see whether the installation of an app was successful. 

error message when installing selfhosted app

Note! Please note that the installation of an app on a device can sometimes take 20 minutes or longer. Please be patient!

In this overview, we explain which error messages can appear as a status if the installation has failed and what the individual messages mean.

StatusBedeutung
Managed but uninstalled
The app has been installed but is no longer on the device.
FailedExact error could not be specified.
Package blocked
The operation failed because it was blocked. For example, a device policy may be blocking the operation, a package verifier may have blocked the operation, or the app may be required for core system operation.
Package invalid
The operation failed because one or more of the APKs was invalid. For example, they might be malformed, corrupt, incorrectly signed, mismatched, etc.
Package conflict
The operation failed because it conflicts (or is inconsistent with) with another package already installed on the device. For example, an existing permission, incompatible certificates, etc. The user may be able to uninstall another app to fix the issue.
Storage conflict
The operation failed because of storage issues. For example, the device may be running low on space, or external media may be unavailable. The user may be able to help free space or insert different external media.
Incompatible device
The operation failed because it is fundamentally incompatible with this device. For example, the app may require a hardware feature that doesn't exist, it may be missing native code for the ABIs supported by the device, or it requires a newer SDK version, etc. Starting in Build.VERSION_CODES.UPSIDE_DOWN_CAKE, an app with only 32-bit native code can still be installed on a device that supports both 64-bit and 32-bit ABIs. However, a warning dialog will be displayed when the app is launched.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.