Inspecting Android installation errors with adb logcat
Using Android Platform Tools (adb logcat and adb install) to pinpoint exact PackageManager failure reasons.
Why Android shows "App not installed"
Android's on-device Package Installer summarizes dozens of distinct verification failures under a single "App not installed" message. Connecting the device to adb reveals the exact INSTALL_FAILED_* constant in seconds.
Capturing PackageManager logs with adb logcat
- Enable Developer options and USB debugging on the Android phone (
Settings -> About phone -> tap Build number 7 times). - Connect via USB (or Wireless Debugging) and filter
logcatfor package installation events while tapping Install on the device:
adb logcat -c
adb logcat | grep -iE "PackageManager|InstallStaging|PackageInstaller"
Testing the APK directly from a computer
You can also run adb install against the local .apk to print the verbose failure code immediately:
adb install -r path/to/YourApp.apk
Common PackageManager error codes
INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing app on device is signed with a different certificate—runadb uninstall com.your.packagefirst.INSTALL_FAILED_VERSION_DOWNGRADE: Installed app has a higherversionCode.INSTALL_FAILED_NO_MATCHING_ABIS: APK native libraries (lib/x86_64) do not support the device CPU (arm64-v8a).INSTALL_PARSE_FAILED_NO_CERTIFICATES: APK was built without v1/v2 signing or modified after signing.INSTALL_FAILED_OLDER_SDK: Device Android API level is below the APK'sminSdkVersion.