"App not installed": what Android is actually telling you
Android says App not installed and nothing else. Behind that one line sit several unrelated problems, and the fix depends entirely on which one you hit. Work down this list in order: the causes are ordered by how often they turn out to be the real one.
1. A different signature from the copy you already have
This is the most common cause by far. Android refuses to replace an installed app with one signed by a different key, because that is exactly what a malicious swap would look like. It does not matter that the version number is higher.
The fix: uninstall the existing app first, then install the new file. You will lose local data unless the app backs up to a cloud account, so sign in and sync before you uninstall.
Publicité
2. A split app installed from only its base APK
Large apps ship as a base APK plus split APKs for your architecture, screen density and language. Install the base alone and you get either this error or an app that opens and immediately crashes.
The fix: download the XAPK or APKS version instead and open it with an installer, which puts every part in place in one transaction.
Handles XAPK, APKS and APKM files, installs the base and its splits together, and copies OBB data to the right folder.
3. The app needs a newer Android than the phone has
Every APK declares a minimum SDK version. If your phone is below it the installer refuses, and the message is the same generic one.
The fix: find an older release of the app. Version history pages list the minimum Android for each build, so pick the newest one your phone accepts rather than the newest one that exists.
| Android version | API level | Typical minimum today |
|---|---|---|
| Android 8 / 8.1 | 26 / 27 | Below most current apps |
| Android 10 | 29 | Still supported by most apps |
| Android 12 and newer | 31+ | Everything current installs |
4. Not enough free storage, even when it looks like there is
Installing needs room for the archive, the unpacked app and the optimised code at the same time, so a 500 MB game can need two or three times that free. Android reports the failure as this same message.
The fix: free noticeably more than the file size, clear the Play Store and installer caches, and install to internal storage rather than an SD card.
5. The less common ones
- A corrupted or partial download, so download it again
- Install from unknown sources not granted to the app you are installing from
- A work profile or device policy blocking sideloading
- An ARM-only build on an x86 emulator, or the reverse
- Needing root, which none of this requires
- The file being 'too old', since old versions install fine
- Airplane mode or no connection, which does not block a local install
The order to try things in
- Uninstall any existing copy Fixes the signature clash, which is most cases.
- Check you have the right file type If it is a big app, take the XAPK and use an installer.
- Check the minimum Android version Then pick an older build if your phone is below it.
- Free two to three times the file size Then retry.
- Download the file again A truncated download fails at the very end of the install.
Nine times out of ten it is the signature clash, and the fix is to uninstall the old copy first. If that does not do it, the file type is the next thing to check.
Frequently asked questions
Does uninstalling lose my data?
Local data, yes. Anything synced to an account comes back after you sign in. Sign in and force a sync before uninstalling, not after.
Can I install an older version over a newer one?
Not without uninstalling first. Android blocks downgrades because the older code may not understand the newer data format.
The install finishes but the app crashes on launch. Same problem?
Usually the split-APK one. The base installed, the resources it needs did not, and the crash happens the moment it looks for them. Install the XAPK instead.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
