You've downloaded an APK from a trusted site, tapped it, and instead of the install button, you get a grayed-out screen with "App not installed." Sometimes it pops up immediately; other times it waits until the progress bar hits 100%. It happens most often after you've already had the app installed before, or when you're trying to install a newer version over an older one. A few folks hit it on a fresh install when storage is tight or the file got corrupted mid-download.
Why does this happen?
Android rejects the install for a handful of reasons, and the error message doesn't tell you which one. The likely culprits are:
- Signature mismatch – The APK you have is signed with a different certificate than the one already on your phone. That's common when you're downgrading from a Play Store version to an older APK, or when the developer signed a debug build.
- Package conflict – A leftover app or partial install is blocking the new one.
- Insufficient storage – Even if you have a few GB free, some apps need contiguous space, and Android's package installer can be picky.
- Corrupted APK – The download didn't finish properly, or the file got truncated.
- Installation blocked – You haven't granted permission for that browser or file manager to install unknown apps.
The real fix depends on which cause is yours, so try these steps in order until one works.
Step-by-step fix
Step 1: Allow unknown sources for the app you're using
If you're downloading via Chrome or opening from a file manager, that app needs special permission. On Android 8 and later, go to Settings > Apps > [Your browser or file manager] > Advanced > Install unknown apps. Toggle on Allow from this source. After you do that, go back and try the APK again. You should see the install button now, not a block message.
Step 2: Uninstall the existing app (if you have it)
If the app is already installed and you're trying to install an APK with a different signature, you'll hit 'App not installed' every time. Go to Settings > Apps, find the app, tap Uninstall. Then install the APK fresh. This wipes the app's data, so back up anything important first. After uninstalling, the new APK should install without complaint.
Step 3: Clear the package installer's cache
Sometimes the system's installer gets stuck. Go to Settings > Apps > Show system apps (the three-dot menu on some phones). Find Package Installer, or on Samsung it's called Package install. Tap Storage, then Clear cache. Also hit Clear data if you're desperate – it doesn't remove any of your apps, just resets the installer. Then try the APK again.
Step 4: Free up storage space
On Pixel phones, you need at least 500 MB free for a large app. On budget phones, the package installer can be even pickier. Go to Settings > Storage and see what's using space. Delete old videos, clear cached data from apps you don't use, and uninstall a couple of games you haven't touched in months. After freeing space, retry the install.
Step 5: Re-download the APK file
Corruption isn't always obvious. Delete the APK you downloaded, go back to the source, and download it again. If you're using Chrome, check the notification bar – sometimes it says 'Download complete' but the file is actually truncated. Also, make sure you're downloading the correct version for your device architecture (ARM vs ARM64). Most modern phones are ARM64, but a few older ones aren't.
Step 6: Disable Play Protect temporarily
Google Play Protect can block installs it deems suspicious, and it doesn't always show a warning. Open the Play Store, tap your profile icon, go to Play Protect, then tap the gear icon to access settings. Toggle off Scan apps with Play Protect. Try the install again. If it works, turn it back on after – you're just bypassing a false positive here, not nuking your security.
Step 7: Use ADB to install (for stubborn cases)
If none of the above worked, ADB (Android Debug Bridge) can give you a detailed error message instead of the generic one. On your computer, install ADB (platform-tools from Google). On your phone, enable Developer options (tap the build number 7 times in Settings > About phone), then turn on USB debugging. Plug your phone in, and on the computer run:
adb install -r /path/to/your-app.apkThe -r flag replaces the existing app. If that fails, ADB prints a specific error like INSTALL_FAILED_UPDATE_INCOMPATIBLE or INSTALL_FAILED_INSUFFICIENT_STORAGE. That tells you exactly what's wrong. For a signature mismatch, you'll see INSTALL_FAILED_UPDATE_INCOMPATIBLE or INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. If it's a signature issue, you'll need to uninstall the existing app first (Step 2) – ADB won't bypass that.
If it still fails
You've tried all seven steps and the error persists? Here's where to look next.
- Check if the APK is actually for your device – Look at the CPU architecture. Apps built for x86 won't run on ARM. Some APKs are split by density or API level, and sideloading the wrong split can fail.
- Check the file's integrity – Compare the file size on the download page to what you have. If they don't match, re-download.
- Try a different APK source – If you're pulling from a random site, the file could be repackaged and signed incorrectly. Stick to known aggregators like APKMirror or the developer's official site.
- Restart your phone – It clears the package installer's temporary files and sometimes fixes weird state issues.
One more thing: if you're trying to install an app that's not compatible with your Android version, no step here will help. The app won't install, period. In that case, you need an older version of the app or a different device.
Most of the time, Step 2 (uninstall the old app) or Step 5 (re-download) fixes it. The rest are for the rare cases where Android's installer just gets cranky.