What causes APK install failures when deploying a Unity build to Android?

adb could not install the build — a signature conflict with the installed copy, insufficient storage, a disallowed downgrade, an ABI the device lacks, or a flaky cable/unauthorized device.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix “CommandInvokationFailure: Unable to install APK to device” in Unity

Quick answer: Read the installer's actual failure code in the message (INSTALL_FAILED_*), uninstall the conflicting copy or fix the ABI/version mismatch, and re-run with a verified adb connection.

Build succeeds, deploy fails: the key is the INSTALL_FAILED_ code buried in the message, which names the exact reason. Here is the decoder and fix for each common one.

How to fix it

1. Decode the INSTALL_FAILED code

UPDATE_INCOMPATIBLE: the device copy is signed with a different key — uninstall it. VERSION_DOWNGRADE: bump version code or uninstall. NO_MATCHING_ABIS: your build's architectures exclude this device. INSUFFICIENT_STORAGE: free space.

2. Uninstall conflicting installs completely

Store builds, CI builds, and local debug builds sign differently. adb uninstall com.yourstudio.game clears the conflict — remember multi-user devices may need per-user uninstalls.

3. Match ABIs to the device

Enable ARM64 (and ARMv7 if you support old devices) in Player Settings; an x86-only or ARMv7-only build refuses to install on modern ARM64-only phones.

4. Verify the adb link

adb devices must list the device as device, not unauthorized or offline — replug, accept the RSA prompt, and prefer a data-capable cable.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.