APK Install Failed Error Codes: Complete Guide to INSTALL_FAILED & Android Installation Errors (2026)

INSTALL_FAILED_NO_MATCHING_ABIS — What does that even mean?
Error -28 — Is my phone broken?
The package appears to be corrupt — But I just downloaded it!

When you install APK files outside of Google Play, Android runs a series of security checks. Any failure throws a cryptic error code that tells you almost nothing as a regular user.

This guide is your complete reference manual for APK installation errors on Android. Every common code, what causes it, and how to fix it.

Quick Reference Table

Most Common Error Codes — Explained

1. INSTALL_FAILED_INVALID_APK (Most Generic)

Message: "App not installed. The package appears to be corrupt."

Causes:

1. APK was corrupted during download or transfer
2. APK signature is invalid or the file was tampered with
3. APK was built for a different Android platform (e.g., Android TV or Wear OS)

Fix:

→ Delete the corrupted APK
→ Re-download from gptoapk.com (Google Play direct extraction)
→ Verify file size matches the expected size
→ Use apksigner to check signature integrity:
   apksigner verify -v app.apk

2. INSTALL_FAILED_NO_MATCHING_ABIS

Message: "INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113"

Why it happens: The APK contains native code (.so libraries) compiled for a different CPU architecture than your phone.

Phone architectures:

• arm64-v8a — Standard for 2020+ phones (64-bit)
• armeabi-v7a — Older phones (32-bit)
• x86_64 / x86 — Rare Intel-based Android devices

Check your phone:

adb shell getprop ro.product.cpu.abi

Fix:

arm64-v8a phone: download arm64-v8a version of the APK
armeabi-v7a phone: download armeabi-v7a or universal version
Note: Some old APKs contain only armeabi-v7a libraries and won't work on pure 64-bit phones

3. INSTALL_FAILED_UPDATE_INCOMPATIBLE

Message: "INSTALL_FAILED_UPDATE_INCOMPATIBLE"

What it means: An app with the same package name is already installed, but with a different signature key.

Typical scenario:

You installed WhatsApp from Google Play (Signature A)
→ Downloaded WhatsApp APK from a website (Signature B)
→ Android refuses to overwrite because signatures don't match

Fix:

Uninstall the existing app → Install the new APK
⚠️ Warning: Uninstalling deletes all app data (messages, settings, etc.)

4. Error -11

Message: A numeric error code without a helpful description.

Most common cause:

• The APK file was truncated during download
• The download didn't complete

Fix:

→ Delete the APK
→ Download again from a reliable source (gptoapk.com)
→ Make sure the download completes 100%
→ Don't transfer APK files via messaging apps (WhatsApp, WeChat rename them)

5. Error -28 (ABI Variant)

Message: Just "INSTALL_FAILED: -28"

Why: Same underlying cause as INSTALL_FAILED_NO_MATCHING_ABIS — the APK's native libraries don't match your CPU.

Fix:

On gptoapk.com, check the "Architecture" field for each APK
Download the version that matches: arm64-v8a, armeabi-v7a, or universal

6. Error -29 (V1 Signature Blocked)

Message: "INSTALL_FAILED: -29"

Why: The APK uses only V1 (JAR) signing, which is blocked on Android 14+.

Fix:

→ Look for a newer version of the app (with V2/V3 signing)
→ Install on an older Android device (Android 13 or below)
→ Ask the developer to update their signing scheme

7. Error -24 (Update Conflict)

Message: "INSTALL_FAILED: -24"

Why: An app with the same package name but a different developer signature is already installed.

Fix:

Settings → Apps → [App Name] → Uninstall → Reinstall the new APK

8. INSTALL_FAILED_INSUFFICIENT_STORAGE

Message: "Not enough storage space"

Why: Your device's data partition doesn't have enough free space.

Check:

Settings → Storage → Check available space
If less than 500MB is free, many apps will refuse to install

Fix:

→ Clear app caches (Settings → Storage → Cache data → Clear)
→ Uninstall apps you don't use
→ Clear WeChat/WhatsApp file caches
→ Move photos to cloud/computer storage
→ Use your phone's built-in cleaner tool

Less Common But Important Errors

INSTALL_FAILED_DEXOPT

DEX optimization failure. Usually happens on low-memory devices or when Android system files are corrupt.

Fix:

→ Restart phone and try again
→ Clear Dalvik cache (requires Recovery mode)
→ If that doesn't work, factory reset may be needed

INSTALL_FAILED_UID_CHANGED

Android remembers the UID of previously installed apps. If you install the same package with a different signature, UID conflicts occur.

Fix:

adb shell pm remove <package-name>
# Or factory reset as a last resort

INSTALL_FAILED_SHARED_USER_INCOMPATIBLE

Two apps declare the same sharedUserId but have different signatures.

Fix:

→ Uninstall the other apps that share the user ID
→ Ensure all shared-user apps use the same signature

INSTALL_FAILED_MISSING_SHARED_LIBRARY

The APK needs a system library (like Google Maps library) that's not on your phone.

Fix:

→ Install Google Play Services
→ Some Chinese ROMs simply don't include certain Google libraries
→ This is a manufacturer limitation, not something you can easily fix

Error -112 (Version Downgrade)

You're trying to install an APK with a lower version code than the installed app.

Fix via ADB:

adb install -r -d app.apk

Error -505

Why: A permission declared by the APK is already claimed by another installed app.

Fix:

Uninstall the conflicting app → Install your target app → Reinstall the other app

The Universal Troubleshooting Flowchart

APK install failing?
│
├─ "Parse error" / "Package corrupt"
│  ├─ Re-download → Try again (90% fixed)
│  └─ Still fails → Change source (gptoapk.com)
│
├─ "INSTALL_FAILED_NO_MATCHING_ABIS" or Error -28
│  ├─ Check phone ABI (adb shell getprop ro.product.cpu.abi)
│  └─ Download APK for the correct architecture
│
├─ "INSTALL_FAILED_UPDATE_INCOMPATIBLE" or Error -24
│  └─ Uninstall old version → Install new APK
│
├─ Error -11
│  └─ Re-download complete APK (don't transfer via chat apps)
│
├─ Error -29
│  └─ Find a V2/V3 signed version of the app
│
├─ "Insufficient storage" or Error -110
│  └─ Free up phone storage
│
└─ Other obscure error
   └─ Advanced debugging (see table below)

Prevention: How to Avoid Installation Errors

Check Before Downloading

Good Download Habits

• Download from Google Play whenever possible (zero errors)
• Use gptoapk.com for Google Play-extracted APKs
• Don't transfer APKs via WhatsApp/WeChat — they rename or corrupt files
• Verify file size after download before trying to install

2026 Installation Restrictions Update

Android 15 Changes

OEM Differences

Summary

APK installation errors look scary, but they're almost always caused by one of three things:

80% of errors = Corrupt download + Wrong architecture + Signature conflict

If you download from gptoapk.com (which extracts APKs directly from Google Play with original signatures), most errors won't even happen.

Keep these ADB commands handy:

# Check architecture
adb shell getprop ro.product.cpu.abi

# Force install (preserve data + allow downgrade)
adb install -r -d app.apk

# Uninstall app
adb uninstall com.example.app

# Check APK signature
apksigner verify -v app.apk

Remember: If an APK consistently fails installation from multiple sources, it's probably a defective or malicious file. Don't force it — find a clean version.

Last updated: June 1, 2026. Android installation error codes may change with system updates.

Related guides:

• Google Play Not Opening? 11 Fixes
• Fix Google Play "Device Not Compatible" Error
• How to Fix APK Signature Verification Failed

Keywords: APK install failed, INSTALL_FAILED error codes, Android install errors, APK error codes 2026, sideload Android apps, APK installation problems, gptoapk