You've downloaded an APK from a friend or a site, tap it, and bam — "App not installed." No explanation, just that dead end. This usually happens when you're sideloading an app that's already on your phone, when the APK is corrupted, or when your phone's installer hits a wall it can't explain.
The root cause is almost always one of three things: the app's signing certificate doesn't match what's already installed, you're out of storage (actually out, not just close), or the package installer is choking on a malformed APK. Rarely, it's a leftover data folder from a previous install that confuses the system.
Here's the thing — the error message is useless. It doesn't tell you which of these it is. So you'll work through them in order, and one of these will get you there.
Step 1: Free Up Real Storage Space
Go to Settings > Storage and look at the actual free space. Not the "available" number — that's misleading. On some Samsung and Xiaomi phones, the system reserves a chunk, so if you see less than 500MB free, that's your problem. The installer needs room to unpack the APK and then install it, and it doesn't do it in the space you see. Delete a few videos, clear your downloads folder, then retry.
Step 2: Check for an Existing Install (Signing Key Conflict)
If the app is already on your phone — even an older version — the new APK must be signed with the same key. If it's not, Android refuses to overwrite it. This is the classic "app not installed" trigger when you're testing your own builds or grabbing a modded APK.
Check if the app exists: go to Settings > Apps, search for the app name. If it's there, you have two options:
- Uninstall the existing version, then install the new APK. This loses the app's data, so back up anything important first.
- If you're the developer, match the signing key in your build. Use the same keystore and alias as before.
I've seen people factory reset their phones over this, and it's overkill. Just uninstall the old app, and you're good.
Step 3: Force Stop the Package Installer
Sometimes the installer itself gets stuck. Head to Settings > Apps > Show system apps (you might need to tap the three-dot menu), find Package Installer (or Google Play Store on some devices), then Force stop and Clear cache. Don't clear data unless you want to reset app preferences — just cache is fine.
This tripped me up the first time a client's Pixel 6 wouldn't install anything. A force stop fixed it in ten seconds.
Step 4: Verify the APK Isn't Corrupt
If the APK is incomplete or corrupted, the installer bails. Check the file size against the expected size from the source. If you downloaded it on mobile and it's a few KB smaller than it should be, redownload it — ideally with a stable Wi-Fi connection. Also, try a different browser or download manager; sometimes the download gets cut off silently.
For a quick integrity check on a PC, use sha256sum if you have the official hash:
sha256sum your-app.apkCompare that to the hash the developer lists. If it doesn't match, the file's bad.
Step 5: Clear the 'Package Installer' Data (Nuclear Option)
If steps 1–4 failed, go nuclear on the installer. Settings > Apps > Show system apps > Package Installer > Storage > Clear data. This resets the installer's state, which fixes weird permission glitches. You'll lose nothing important — just the installer's temporary files.
After this, try installing again. If it still fails, you're down to the last culprit.
Step 6: Check for Leftover Data Folders
On some phones, even after uninstalling an app, a folder remains in /data/data/ or /data/app/. A new install with a different signature will clash with that leftover. You can't see this without root, so here's the practical fix: use a file manager with root access if you have it (e.g., Solid Explorer) and delete the corresponding folder. No root? Then factory reset is your last resort — but I'd only do that after trying every other step, because it's a pain.
Still Getting 'App Not Installed'?
If you've done all this and it's still failing, the APK itself is likely bad — either it's an incompatible architecture (e.g., an ARM-only app on a 64-bit-only device) or it's a fake/malware APK. Try downloading from the official source or an alternate trusted mirror. Also check your Android version — some newer APKs require Android 10 or higher, and if you're on an older version, no amount of clearing cache will help.
One last thing: if you're on a corporate device with a managed profile, your IT policy might block sideloading entirely. That's not something you can fix with settings — you'll need to ask your admin. But for everyone else, one of these steps will get you there. I've uninstalled the old app more times than I can count, and it's still the most common fix.