INSTALL_PARSE_FAILED_NO_CERTIFICATES / App not installed as package appears to be invalid
The APK isn’t signed (or the signature is invalid for this Android version), so it can’t be installed.
Seen on:
Android
Meaning
Release APKs built without a signingConfig are unsigned. Modern Android needs APK Signature Scheme v2+; signing with only v1 or modifying the APK after signing breaks it. Phones show “App not installed as package appears to be invalid”.
Common causes
- Release build without signingConfig
- APK modified (zipaligned) after signing
- Only v1 (JAR) signature on Android 11+ (targetSdk 30+)
- Corrupted download
⚡ Quick fix
- Configure signingConfig for release or sign with apksigner
- zipalign before apksigner, never after
- Verify with apksigner verify
Detailed fix by platform
Shell
- kotlin
zipalign -v -p 4 app-unsigned.apk app-aligned.apk apksigner sign --ks release.jks --out app-signed.apk app-aligned.apk apksigner verify --verbose app-signed.apk
How to diagnose
- Signature — apksigner verify output
- Build — signingConfig set?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ApiException: 10 Google Sign-In: com.google.android.gms.common.api.ApiException: 10 (DEVELOPER_ERROR)
- gpg failed to sign error: gpg failed to sign the data — fatal: failed to write commit object
- INSTALL_FAILED_INSUFFICIENT_STORAGE INSTALL_FAILED_INSUFFICIENT_STORAGE: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
Most viewed in Android
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026