You tap the APK, the installer spins for a few seconds, and then — flatly — "App not installed." No reason given, no error code, nothing to Google. It's one of Android's least helpful messages, because it covers half a dozen completely different problems: a corrupted download, no room left on the phone, a signature clash with an app you already have, or a security setting quietly vetoing the install. Eight fixes below, in the order I'd actually try them.
Quick Answer: Most "App not installed" errors come down to three things: not enough free storage, a corrupted APK download, or a signature conflict with an already-installed copy of the app. Free up space (Settings → Storage), re-download the APK from a trusted source, and if the app is already installed, uninstall it first — then try again.
In This Guide:
- Why You Get "App Not Installed"
- Fix 1: Free Up Storage Space
- Fix 2: Allow Install From Unknown Sources
- Fix 3: Re-download the APK (Corrupt File)
- Fix 4: Check Android Version Compatibility
- Fix 5: Remove the Conflicting Existing App
- Fix 6: Check Play Protect Isn't Blocking It
- Fix 7: Reset App Preferences
- Fix 8: Install From the Play Store Instead
- What If Nothing Works?
- FAQs
Why You Get "App Not Installed"
Android refuses an install for specific reasons — it just doesn't bother telling you which one. The lineup:
- Corrupted APK — the download got interrupted or the file is damaged. Most common with sideloaded APKs.
- Not enough storage — the installer needs free space beyond the APK size for unpacking.
- Signature conflict — an app with the same package name but a different developer signature is already installed. Android won't overwrite it.
- Incompatible Android version — the APK needs a newer (or sometimes older) Android than your phone runs.
- Blocked by security settings — unknown-source installs not allowed, or Play Protect flagged the file.
- Damaged storage / SD card — installing to a flaky SD card fails silently with this exact message.
Fix 1: Free Up Storage Space
The installer needs breathing room — roughly twice the APK's size free, since it unpacks during install. A phone showing "500 MB free" can still fail a 300 MB install:
- Check Settings → Storage — if you're under ~1 GB free, that's your problem.
- Clear cached junk: Settings → Storage → Free up space (or use Files by Google → Clean).
- Delete a few large videos or move photos to Google Photos / cloud backup.
- Try the install again.
Samsung: Settings → Battery and device care → Storage has a one-tap cleanup.
Xiaomi: the built-in Security app → Cleaner does the same job.
Fix 2: Allow Install From Unknown Sources
Since Android 8, the old global "Unknown sources" switch is gone — permission is granted per app (usually your browser or file manager). If it's off, installs die with our exact error:
- Open Settings → Apps → Special app access → Install unknown apps (Samsung: Settings → Apps → ⋮ → Special access → Install unknown apps).
- Tap the app you're installing from (Chrome, your file manager, etc.) and toggle Allow from this source ON.
- Run the APK again.
Fix 3: Re-download the APK (Corrupt File)
A download that "completed" isn't necessarily intact — one dropped packet and the signature check fails at install time:
- Delete the APK file you have.
- Re-download it, preferably on stable Wi-Fi rather than mobile data.
- Stick to reputable sources (the developer's site, APKMirror, or the Play Store). Random APK sites are the top source of corrupted — and malicious — files.
- Check the file size matches what's listed on the download page before installing.
Fix 4: Check Android Version Compatibility
An APK built for Android 14 won't install on Android 10, and some very old APKs refuse to install on Android 12+ because of new signature requirements:
- Check your version: Settings → About phone → Android version.
- Compare with the app's requirements on its download page.
- Too old? Look for an older version of the app built for your Android (APKMirror keeps version history).
- System update available? Settings → About phone → tap the version card → Check for updates (Xiaomi: tap the HyperOS version card; Samsung: Settings → Software update → Download and install).
Fix 5: Remove the Conflicting Existing App
This is the sneaky one. If any version of the app is already installed — even a modded or older build signed by someone else — Android blocks the new install rather than overwriting it:
- Settings → Apps → search for the app name.
- If it's there (even disabled), uninstall it completely.
- Also check for dual/cloned copies (Xiaomi Dual apps, Samsung Secure Folder) — a clone counts as an installed copy.
- Install the new APK fresh.
Back up the app's data first if you care about it — uninstalling wipes it.
Fix 6: Check Play Protect Isn't Blocking It
Play Protect scans sideloaded APKs and can silently kill installs it dislikes:
- Play Store → profile icon → Play Protect → ⚙ settings.
- If "Scan apps with Play Protect" is blocking this specific install, you can temporarily turn off "Improve harmful app detection", install, then turn it back on.
- Only do this for APKs you genuinely trust. Leave the main Play Protect switch on.
Fix 7: Reset App Preferences
Corrupted installer state (usually the Package Installer system app) can wedge installs. Resetting app preferences clears it without deleting anything:
- Settings → Apps → ⋮ → Reset app preferences → confirm.
- No data is deleted — it just resets disabled apps, notification blocks, and default associations.
- Retry the install.
Fix 8: Install From the Play Store Instead
If the app exists on the Play Store, that's the path of least resistance — the Store handles compatibility, signatures, and updates for you:
- Search the Play Store for the app and install it there.
- If the Store says "not compatible", that's your answer: the APK was never going to work on this phone either.
- For paid apps you own elsewhere, the Store version also keeps your license valid.
What If Nothing Works?
- SD card trouble: if you're installing to external storage, move the APK to internal storage and install from there — flaky cards cause exactly this error.
- Try a different APK variant: many apps ship per-architecture builds (arm64 vs armeabi). Grab the one matching your phone — Droid Hardware Info (free) shows your CPU architecture.
- ADB install: from a computer, adb install app.apk gives you the real error message instead of the useless generic one.
- Factory reset: absolute last resort for a broken package manager. Back up everything first.
Watch: App Not Installed Error Fixed Step by Step
Prefer a walkthrough? This video covers the 'App Not Installed' error step by step:
Video by Get Droid Tips — full credit to the creator.
Related Guides:
FAQs
Why does it say app not installed when I have enough space?
The usual culprits then are a corrupted APK (re-download it) or a signature conflict with an already-installed copy of the app (uninstall the old one first).
Can Play Protect cause the app not installed error?
Yes — Play Protect can silently block sideloaded APKs it flags. Check Play Store → profile → Play Protect if a trusted APK keeps failing.
Does resetting app preferences delete my apps?
No. It only resets disabled states, notification blocks, and default-app choices. Your apps and their data stay exactly where they are.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
