You tap Install, the progress bar runs, and then a flat two-word refusal: “App not installed.” No code, no reason, no hint about what to change. That vagueness is the whole problem with this error. Android uses the same message for a dozen unrelated failures — a full storage, a blocked installer, a damaged download, a signature clash with the copy already on your phone, or a file built for a different device. The fix depends entirely on which one you are facing, so this guide starts by narrowing it down instead of asking you to repeat the same tap and hope.
Quick Answer
First check Settings > Storage — you need well over the APK’s size free, ideally 1 GB or more. Then grant the exact app you are installing from (browser, file manager, or messaging app) permission under Settings > Apps > Special app access > Install unknown apps. If it still fails, delete the file and re-download it on stable Wi-Fi, because a partial download fails Android’s signature check with this same generic message. If you already have the app installed, a signature mismatch is the likely cause — update from the original source instead of a different one.
In This Guide
- 1. Free up storage — more than just the APK’s size
- 2. Allow Install unknown apps for the exact source app
- 3. Delete the file and re-download a clean copy
- 4. Resolve the signature or version conflict with the installed copy
- 5. Check compatibility and missing split APK files
- 6. Clear the Package Installer cache and check Play Protect
- Frequently Asked Questions
One clue helps before you start: think about when it fails. Blocked instantly, before any progress bar, points to permission or Play Protect. A bar that finishes and then fails points to a damaged file or a signature problem. Failing only when updating an app you already own points to a signature or version conflict. Keep that clue in mind as you work through the fixes below, in the order most likely to match your case.
1. Free up storage — more than just the APK’s size
Android does not just copy the APK into place. It unpacks it, verifies it, and builds the installed app, which needs considerably more free space than the file itself. A phone showing 200 MB free will refuse a 100 MB install without ever explaining why.
- Open Settings > Storage and read the free-space figure honestly. For most installs, aim for at least 1 GB free.
- Free space by clearing app caches, deleting large downloaded videos, or moving photos to cloud backup — start with the biggest items Storage lists.
- Delete any failed or duplicate copies of the same APK in Downloads, so the installer is not tripping over a partial file.
- Try the install again once the free space is comfortably above the APK’s size.
If storage is already plentiful, move on — but do not skip the check.
2. Allow Install unknown apps for the exact source app
Since Android 8, there is no single “unknown sources” switch. Each app that hands Android a file needs its own permission — your browser needs it if you downloaded the APK in Chrome, your file manager needs it if you tapped the file there, and a messaging app needs it if the file arrived in a chat. Granting the wrong app changes nothing.

- Go to Settings > Apps > Special app access > Install unknown apps. On Samsung phones the path runs through Apps > the three-dot menu > Special access; on Xiaomi phones it sits under Privacy protection > Special permissions.
- Find the exact app you are installing from — the browser or file manager you tapped the file in.
- Turn on Allow from this source for that app only.
- Go back and tap the APK again. Do not grant this permission to apps you do not recognise, and switch it off again afterwards if you prefer.
If the install is blocked instantly with no progress bar at all, this permission is the first suspect. Note the difference from a related problem: if the whole Install unknown apps option is greyed out rather than simply off, that is a separate device-policy issue, covered in its own guide linked below.
3. Delete the file and re-download a clean copy
Every APK carries a digital signature that Android checks byte for byte before unpacking. A download interrupted by a Wi-Fi drop, a browser crash, or a switch between networks can look complete in the file manager while failing that check — and the only message you get is “App not installed.”
- Delete the APK you have. Do not try to repair it or install over it.
- Re-download it from the original, trusted source on stable Wi-Fi, and wait until the download fully completes before tapping it.
- Compare the file size with the size the source lists, if it lists one. A file noticeably smaller than expected is still incomplete.
- Install the fresh copy and see whether the error is gone.
Re-downloading feels too simple to matter, which is why people skip it and spend an hour in settings instead. In practice, a corrupted download is one of the top causes of this error, especially for large files downloaded on an unstable connection. If the same fresh file fails on one phone but installs fine on another, the cause is compatibility, not corruption — see fix 5.
4. Resolve the signature or version conflict with the installed copy
This is the cause behind most “it worked before, now it won’t update” cases. Android treats an app’s signing certificate as its identity. If the copy already on your phone came from Google Play and the new file comes from a different source — or from a different APK mirror — the certificates do not match, and Android refuses the update to stop one app impersonating another. Trying an older version than the installed one produces the same refusal.
- Check whether the app is already installed, even if you forgot about it: Settings > Apps, search for the app name.
- If it is installed, first try updating it from the same source it came from — Play Store for a Play Store copy, the developer’s own channel for a sideloaded copy.
- Only if you genuinely need the new file’s source: back up the app’s data first (its own backup or export, where available), then uninstall the old copy, then install the new file fresh.
- Never uninstall first without a backup plan — uninstalling erases the app’s local data, and that loss cannot be undone.
There is no setting that overrides a signature mismatch, and that is deliberate. It is a security rule, not a bug. The correct move is almost always to stay with the original source rather than forcing a different build onto the phone.
5. Check compatibility and missing split APK files
Some APKs are not single files at all. Modern apps are often distributed as split bundles: a base APK plus extra files for the phone’s processor type, screen density, and language. Installing only the base file fails on every device, again with the same generic message. Separately, an APK built for a newer Android version, or for a different processor architecture, will fail silently on an older or incompatible phone.
- Check the source’s requirements before downloading: the minimum Android version, and whether the file is a single APK or a bundle (often labelled APKM, XAPK, or split APK).
- If it is a bundle, install the complete set together with a bundle installer — do not install the base file on its own.
- If your phone runs an older Android version than the app requires, look for an older release of the app built for your version, rather than forcing the newest one.
- If the same file installs on a friend’s phone but not yours, compare Android versions and device models — that difference is usually the answer.
This fix matters most for games and large apps, which are the ones most often split into bundles, and for older phones being handed a build meant for current devices. Covers Android 10 through 14.
6. Clear the Package Installer cache and check Play Protect
When every install fails — not just one file — the installer itself may be stuck, or Play Protect may be blocking the file as suspicious. This final fix addresses both, and it is the last step before considering anything drastic.

- Go to Settings > Apps, tap See all apps, then find Package installer (on some phones it appears as Google Play services’ installer component — show system apps if it is hidden).
- Tap Storage & cache > Clear cache, then Clear data if the problem persists.
- Restart the phone and try one known-good APK again.
- If Play Protect blocks the specific file, open Settings > Google > Security > Google Play Protect, check what it flagged, and only proceed if you fully trust the source — a blocked file from an unknown source should stay blocked.
A factory reset is sometimes suggested for this error, but treat it strictly as a last resort when no install of any kind works and every fix above has failed — it erases local data across the phone. In most cases the cause is found long before that point, in storage, the source permission, a damaged file, or a signature clash.
Prefer a walkthrough? This video covers fixing the “App not installed” error on Android step by step:
Video by Make knowledge free
Related Guides
Frequently Asked Questions
Why does Android say “App not installed” with no other detail?
Android shows one generic message for many different install failures — storage, permissions, corruption, signature mismatch, and compatibility all share it. The timing gives a clue: instant blocking points to permission or Play Protect, while a bar that finishes then fails points to a damaged file or signature problem.
Can I install an APK over a Play Store version of the same app?
Usually not. Android compares signing certificates on update, and a Play Store copy and a sideloaded copy are normally signed with different keys. Update from the original source instead, or back up the app’s data, uninstall the old copy, and install the new one fresh.
Does “App not installed” mean the APK is a virus?
Not necessarily — most cases are storage, permission, corruption, or compatibility problems with legitimate files. Still, only install APKs from sources you trust, and if Play Protect flags a file from an unknown source, leave it blocked rather than forcing it through.
By Sameer Zehri | App Fix Guru Editor | Last updated: November 2026