Android APK Install Failed? Every Error Code Explained (-11, -28, -29 and More)

You finally found the APK you were looking for, tapped install, and got hit with a cryptic error:“There was a problem parsing the package” or “App not installed” or a bare error code -11. Before you redownload it for the fifth time, know this: the vast majority of Android install failures can be fixed once you match the error to its cause. This guide maps the most common APK install errors — especially the notorious -11, -28, and -29 — to concrete fixes.

Key idea: An install failure isn’t random. It’s always one of four categories — a corrupt file, a signature conflict, a compatibility/permission mismatch, or insufficient storage. Translate the code first, then treat the right category.

1. Learn to “translate” the error

Android install errors come in two layers: system-level codes (the ones with -number, from PackageManager) and manufacturer messages(added by each OEM skin — Xiaomi’s “parse error”, Huawei’s “app not installed”, etc.).

The key point: -11, -28, and -29all come from the same layer of low-level conflicts — but they mean very different things. Each gets its own section below.

2. Error -11: the classic signature conflict

The most common trigger for -11 is simple: your phone already has an app with the same package name but a different signature.

Typical scenarios:

• You installed the “official” build from a store, and now you’re installing a modified build from a third-party source. Same package name, different signature — Android refuses to overwrite it.
• You previously had a debug-signed build and now have a release-signed one.

Fixes (in order):

1. Long-press the icon → uninstall the original app, reboot, then install the new APK.
2. If it still fails after uninstalling, you have leftover data. Go to Settings → Apps → find the residue and clear its data, or use a cleaner tool to remove app leftovers.
3. Compare the signature fingerprints of both APKs with an APK analyzer (like MT Manager) to confirm the signatures really differ.
4. Installed it in a dual-app / work profile / second spacetoo? Uninstall that copy as well — it counts as a separate install.

Heads up: back up any data you need before uninstalling.

3. Error -28 / -29: architecture and OS incompatibility

-28 and -29 boil down to the APK not matching your phone. Two common causes:

A. CPU architecture mismatch (ABI)

Android APKs may bundle native libraries for arm64-v8a, armeabi-v7a, or x86_64. If your APK only has x86 (meant for emulators), it will fail or misbehave on a real device.

• How to check:Use a “Device Info” app to see your CPU architecture (most modern phones are arm64-v8a).
• How to fix: Download the arm64-v8a or universalbuild. Many download sites split builds by ABI — picking “universal” is the safest bet.

B. Android version (minSdk) too high

If the APK says “Requires Android 9.0” and your phone is on Android 8.0, it fails immediately.

• How to check:Look at the APK’s minSdkVersion or the download page notes.
• How to fix: Find an older build that supports your version, or consider updating the OS.

Quick rule of thumb: The same APK installs fine for others but not you → likely ABI/OS mismatch (-28/-29). You’ve installed something similar before → likely signature conflict (-11).

4. “Parse error” / “problem parsing the package”: usually the file

Almost every “problem parsing the package” traces back to the file itself:

• Incomplete download— the connection dropped and you only got half the APK. Fix: redownload on a stable connection.
• Corrupted file— a bad transfer. Fix: re-fetch and verify the file size matches the source.
• Renamed extension — some browsers save .apk as .apk.1 or .zip. Fix: rename it back to .apk (the filename, not the contents).
• OS too old— ancient Android versions can’t parse newer package formats.
• Installing from an SD card — some devices fail to parse from external storage. Move the APK to internal storage first.

Quick verification:Copy the APK to a PC and check whether its size matches what the source page lists. A big difference means the download didn’t complete.

5. Not enough storage: don’t be fooled by “ghost” usage

The system says “not enough space” but Settings shows dozens of GB free? Usually one of two things:

1. Installation needs temporary space. Android needs roughly 1.5–3× the APK size free to unpack and install. A 2 GB game may need 4–6 GB of free storage.
2. Uninstall residue. After removal, cached data under /Android/data and /Android/obb often stays behind and piles up.

Cleanup tips: Use the system storage view and clear video and messaging caches first. Manually inspect Android/data (some newer Android versions require a file manager with special permission). Use a cleaner that scans for uninstall leftovers and duplicate files.

6. “Can’t install unknown apps”: permission not granted

This is the most common OEM-level block — not an error code, but it stops more people than anything:

• Since Android 8.0, install permission is granted per app. Go to Settings → Apps → find the app you use to open the APK (browser / file manager) → enable “Allow from this source”.
• Some OEM ROMs (Xiaomi, Huawei, OPPO, vivo) add extra “clean mode / security protection” that must be temporarily disabled to sideload APKs. Re-enable it afterward.

7. Full troubleshooting flow (just follow it)

1. Translate the error→ match it to the table in section 1 to find the category.
2. Check the file → Correct size? .apk extension? Universal build?
3. Check the phone → CPU architecture (arm64?), Android version (≥ minSdk?), free space (≥ 3× APK?).
4. Check old copies→ Any same-package app or residue? Fully uninstall + reboot first.
5. Check permissions→ “Unknown sources” enabled? Clean mode not blocking it?
6. Switch sources→ If everything else fails, redownload from a reliable source.

8. Two things to do before you install

• Verify safety. Upload the APK to a multi-engine scanner like VirusTotal and review the requested permissions.
• Back up your data. Overwriting or reinstalling can wipe app data. Back up anything important first.

On download sources: Rather than gambling on random sites, use a tool focused on Google Play apps so the package and its origin are transparent. Tools like gptoapk.comlet you search by package name and grab official-channel APKs — which cuts down on truncated or repackaged files, the very thing that causes most install failures.

FAQ

Error -11 and it still won’t install after uninstalling?
Check for copies in dual-app / work profile / second space, or clear uninstall residue and reboot before retrying. Comparing signature fingerprints with MT Manager also helps confirm the root cause.

Is the “universal” build always best?
It’s the most compatible but the largest. If storage is tight, pick the build matching your ABI (e.g., arm64-v8a) once you’ve confirmed your architecture. When in doubt, universal is the safe choice.

Parse error persists across multiple redownloads?
Switch sources. A site repeatedly serving the same bad file is common, or the build simply requires a newer Android version. Pulling the original package from a Play link with gptoapk.com gives you a reliable reference file.

How much free space do I need?
At least 3× the APK size. For large games, leave more than twice their installed (unpacked) size, since the install process needs temporary space to decompress.

Is disabling clean mode risky?
Only disable it temporarily for APKs you trust, and re-enable it right after. Never leave it off while installing from unknown sources.

Bottom line: don’t panic when an install fails. Read the code, match it to the category, and walk through file, signature, architecture, space, and permission one by one. Most “install failures” are solved in under ten minutes. Start with gptoapk.com to grab a clean original package from a Play link, then debug from there.