Troubleshooting Android APK installation
Allowing "Install unknown apps", resolving keystore signature conflicts, and handling Google Play Protect prompts.
1. Grant "Install unknown apps" permission to your browser
On Android 8.0 and newer, sideloading is controlled per-app rather than globally:
- Tap the downloaded
.apkin Chrome or your Files app. - When prompted "For your security, your phone currently isn't allowed to install unknown apps from this source", tap Settings.
- Toggle Allow from this source ON, then tap Back and tap Install.
2. Keystore mismatch ("App not installed as package conflicts with an existing package")
Android requires every update to an installed applicationId to be signed with the exact same keystore certificate:
- If the tester already has the Google Play or release-signed version installed and tries to install a debug-signed QA build (or vice versa), Android blocks the update.
- Fix: Uninstall the existing app from the device first (or use
.debugapplicationIdSuffixinbuild.gradleso debug and release builds coexist side by side).
3. Downgrading versionCode
Android blocks installing an APK whose versionCode is lower than the currently installed build unless you uninstall the newer version first.
4. Google Play Protect "Unrecognized app developer" prompt
Pre-release debug and internal QA keystores are not yet indexed by Google Play. If Play Protect displays App scan recommended or Blocked by Play Protect, tap More details -> Install anyway after verifying the link came from your engineering team.