"App not installed": causes and fixes

"App not installed" is how Android ends an APK installation, often without any hint at the reason. On a German forum, one user describes the typical sequence: the installer loads briefly and then the screen simply reads "app wurde nicht installiert" (app not installed). The full path from download to finished app is covered in the guide on how to install a casino app; here we look at the messages that interrupt it.

Among the four casinos covered, only two are affected. 22Bet offers a native Android app as an APK that is not in the Google Play Store, Irwin an app for Android to download. Frumzi and 5Gringos have no native app and no APK; there is no installation there, and so none of these error messages.

What is behind "App not installed"

According to the Android developer documentation, the package installer distinguishes several failure statuses, among them conflict, invalid, incompatible, storage, blocked and aborted. The documentation does not give the German on-screen texts. The German wordings quoted on this page therefore come from forums, not from Google's documentation, and matching them to a status should be read as a pointer.

In one forum thread a helper names three common reasons: not enough storage, an app that is already present, or an app that Android blocks as harmful. Another adviser also lists three: either the phone is not compatible, or the APK is broken, or unknown sources are not allowed.

The last point is disputed. Android blocks apps from sources other than Google Play until you allow the installation of unknown apps, and this consent has to be given before download and installation. One forum adviser still objects that allowing unknown sources will not be the cause; according to him, a missing permission would produce a different message. In addition, some network operators do not allow installation from unknown sources at all. Where the setting lives and how to allow unknown sources for your browser or file manager is explained step by step on a separate page.

Before ruling causes out, write down your smartphone model and Android version. Forum helpers ask for exactly these first.

Package conflict: existing version or different signature

The German forum wording reads: "Die App wurde nicht installiert, da das Paket in Konflikt mit einem bestehenden Paket steht" (the app was not installed because the package conflicts with an existing package). The user reports failing at this message for two months. According to the Android developer documentation it corresponds to the "conflict" case: the new package clashes with one already installed, for example because of incompatible certificates. As a possible fix, the documentation names uninstalling the other app.

The reason lies in the signature. Android requires every APK to be digitally signed before installation and before every update. During an update the system compares the certificates of the new and the installed version and allows it only if they match. A package with a different certificate would be a different app with a different package name. A forum post sums it up in one sentence: the different signature blocks the installation.

Modified apps often carry a different signature from the original. If such a version is on the device, the official file fails on the conflict, and vice versa. Download a casino APK only from the source the operator names itself: for 22Bet that is only the official 22bet website, for Irwin the download icons at the bottom of the casino's home page.

Does the installed version have to go first? Uninstalling can resolve the conflict, but it has a consequence: app-specific files are removed, so locally stored app data is lost. Whether the casino account is affected is not stated; no source describes the account data of the four brands.

Closely related is the attempt to go back to an older version. In forums it fails with the message that the package has an older version code. Both messages often appear during a manual update via APK. Which rules apply when updating a casino app, and why the signature has to stay the same, is explained on the update page.

"There was a problem parsing the package": Android version and device

On the forum the message reads: "beim Parsen des Pakets ist ein Fehler aufgetreten" (an error occurred while parsing the package). The helpers' follow-up questions target two causes: an incompatible Android version and disabled unknown sources. The Android developer documentation lists the first cause as the "incompatible" case: the app fundamentally does not fit the device, for example because a hardware feature is missing, native code for the CPU architecture (ABI) is not included, or a newer Android version is required.

For the version there is a fixed rule. Android prevents installation if the device's API level is below the minimum version the app declares in its manifest as minSdkVersion. Since Android 14 a limit in the other direction applies as well: apps with a targetSdkVersion below 23 can no longer be installed. Apps of this kind that are already installed remain on the device when it is upgraded to Android 14.

For casino APKs, the stated minimum versions sometimes differ. For the 22Bet APK for Android, goal.com names Android 6.0 or newer and a processor from 1.2 GHz, while Uptodown states "Requires Android 7.0 or higher". Which figure applies to the current file is open. For Irwin there is no information on either system requirements or file size.

If the device's Android version is below what the app requires, downloading the same file again will not help. Package requirements and which brands offer an APK at all are collected in the overview of the casino app for Android.

"Package corrupt": incomplete or modified file

"App wurde nicht installiert. Das Paket ist offenbar beschädigt?" (app not installed, the package appears to be corrupt), asks one forum user. Another writes after three hours of attempts that with every version the message says the package is corrupt. According to the Android developer documentation, this message corresponds to the "invalid" case: one or more APKs are malformed, corrupt, incorrectly signed or mismatched.

Often an incompletely downloaded or subsequently modified file is behind it. Comparing the file size with the published values gives a first clue: for the 22Bet APK goal.com names 55.36 MB, Uptodown 53.19 MB. If the file on your device clearly differs from both values, download it again from the official site. For Irwin no size is stated.

Packages made of several parts play a special role. Google Play generates optimised APKs for each device configuration from an app bundle, so-called split APKs. Alongside them, the XAPK format circulates in forums; according to forums it bundles an APK with additional files such as OBB or several split APKs. There is no official Android document on this format.

Not enough storage

The first follow-up question in many threads is whether there is enough storage space. According to the Android developer documentation there is a separate status for this: the device is running low on free space, or external storage is unavailable. Freeing up space can then help. Google's help pages put it like this for Google Play: if your device is low on space, apps may no longer be downloaded and installed. As a basic step they also name a restart.

Storage is not always the cause, though. A user with a Fire tablet gets "app not installed" even after a restart and stresses that there is definitely enough storage space. Then compatibility and blocked packages are the next suspects. Failed APK downloads get the same advice.

Blocked: Play Protect and device policies

One forum adviser explains a rejected installation by saying that Android blocks the app because it is or may be harmful. Google Play Protect checks apps when they are installed and scans the device regularly, including apps from other sources. Potentially harmful apps are reported, disabled or removed. If an app or URL is known to be harmful, Google can block its installation. Unverified apps with sensitive permissions, which are frequently used for financial fraud, can also be prevented from installing.

Another forum message reads "kann nicht geprüft werden" (cannot be verified). For apps from other sources that have never been scanned, Play Protect may recommend a code scan. The forum advice to allow programs from unsafe sources only describes the permission, not the check of the file. How to recognise a genuine file and what a warning means is explained on the page about casino APK safety with all checking steps.

According to the Android developer documentation, the "blocked" status also ends the process: a device policy or a package verifier has stopped the operation. Such policies include parental controls like Family Link on managed devices. After installation another restriction can apply: sensitive settings such as accessibility can be restricted for the new app; according to Google, some steps only apply from Android 13. They can only be unlocked via "Allow restricted settings" in the app info, and Google advises against it unless you trust the developer.

Installer closes without a message

Sometimes no error message appears at all. One user describes the installation window running up to a percentage display, after which the screen folds shut and nothing happens. According to the Android developer documentation there is an "aborted" status for this: the process was actively ended, for example because requested permissions were declined or the session was abandoned. So check whether a permission dialog was waiting in the background or was declined by accident.

Another user reports that the APK file opens a banking app instead of the installation window, in his case the Sparkasse app. The thread offers no solution for this. A more frequent question is how an APK gets from a PC onto the phone. One forum user sends the file to the phone via Bluetooth and opens it there with a file manager; that app then needs its own permission for unknown sources.

No way via APK: web app in the browser

If the installation stays blocked, for instance by a network operator, a device policy or an Android version that is too old, the route without an APK runs through the browser. Frumzi offers no native app and no APK; play takes place without installation in the mobile browser, based on HTML5. The same applies to 5Gringos: no native app, no installation, a compatible mobile browser is enough. How a web app (PWA) in the browser can be placed on the home screen is described on the page about the browser option.