Diagnose Android APK Installation Failures with ADB

An Android installer dialog often indicates a simple failure with two words: "App not installed." This message can suggest numerous issues including incompatible CPU architecture, signature conflicts, lower version codes, insufficient storage, invalid packages, device policy restrictions, or SDK compatibility problems. Guessing about the issue may exacerbate the situation.

Instead, it's recommended to view installation as a series of tests and check each stage using evidence. This guide provides a repeatable debugging workflow using Android Debug Bridge (ADB) and standard Android tooling, beneficial for developers, testers, support teams, and advanced users troubleshooting sideloaded APKs.

Before starting, record the device information: manufacturer and model, Android version and security patch level, APK filename, size, source URL, SHA-256 hash, whether an earlier version of the app is installed, exact error message from Android or Play Protect, and available storage on the device. Do not remove the currently installed app as it could delete local databases, playlists, settings, and downloaded files.

Only uninstall the app if an export or backup option is available. Ensure the computer used for testing is secure and revoke debugging authorization afterward, especially if the computer is shared.

1. Confirm that ADB recognizes the correct device. Connect the device and run "adb devices -l." A successful connection will display the device. Other states like unauthorized, offline, or no device may indicate issues like an unlocked phone, a need for a new cable or USB port, or driver problems. When multiple devices or emulators are connected, explicitly target the intended device using "adb -s DEVICE_SERIAL shell getprop ro.product.model."

2. Examine the APK before installation. Do not rely on the filename for package identification. Use Android SDK Build Tools, such as "aapt dump badging app.apk" or "apkanalyzer manifest application-id app.apk," to obtain the application ID, version code, version name, minimum SDK, and native architectures. Compare these details with the device by running "adb shell getprop ro.build.version.sdk" and "adb shell getprop ro.product.cpu.abilist."

An APK with only arm64-v8a native libraries will not run on a 32-bit-only device, and an APK with a minimum SDK higher than the device's SDK will be rejected by the Android platform.