Android Studio will not install the app: the device supports x86 but the APK only has ARM libraries
Device supports x86, but APK only supports armeabi-v7aShort answer
The package manager looks for native libraries under lib/<abi> that match the device's own ABI. If your APK has none for it, the install fails. Compare the device ABI with the lib folders in the APK, then add the missing ABI to the build, remove a filter that excludes it, or test on a device that matches.
Fix it fast
1Find out which cause you have
Ask the device which ABI it runs, then list the native libraries inside the APK you are installing. The two must share an ABI folder name.
adb shell getprop ro.product.cpu.abi zipinfo -1 app/build/outputs/apk/debug/app-debug.apk | grep '\.so$'2Match what you see, then jump to its fix
- 1
The device prints x86 or x86_64 while the list shows only lib/armeabi-v7a or lib/arm64-v8a files, or the other way roundThe APK has native libraries for another CPU family onlyFix - 2
The build file names a short list of ABIs, or app-<abi>-debug.apk files exist, and the failing device is not in that listabiFilters or ABI splits leave the device's ABI outFix - 3
The APK has lib/armeabi-v7a or lib/x86 files but no lib/arm64-v8a or lib/x86_64 folder, and the target is a recent emulator image or a new phoneOnly 32-bit libraries on a device or emulator that is 64-bit onlyFix
- 1
What does the error look like?
Device supports x86, but APK only supports armeabi-v7aINSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113
Cause 1 of 3
The APK has native libraries for another CPU family only
1Check
When it installs an app, the package manager looks for libraries of the form lib/<primary-abi>/lib<name>.so, and then for the device's secondary ABI. A folder for an ABI the device does not support is never used, so an ARM-only APK finds nothing it can use on an x86 device. The libraries come from your own native code and from any dependency that ships .so files.
adb shell getprop ro.product.cpu.abi
zipinfo -1 app/build/outputs/apk/debug/app-debug.apk | grep '\.so$'2Fix
Build and package libraries for the ABI of the device. In a Gradle build, add it to ndk abiFilters, and use dependency versions that ship binaries for it. If a dependency has no binaries for that ABI, ask its owner, or test on a device or emulator image that matches the ABIs you do have.
// build.gradle.kts, module app
android {
defaultConfig {
ndk {
abiFilters += listOf("armeabi-v7a", "arm64-v8a", "x86", "x86_64")
}
}
}3Verify
Rebuild and list the libraries again: a folder for the device's ABI is now present, and the install works.
./gradlew installDebug
zipinfo -1 app/build/outputs/apk/debug/app-debug.apk | grep '\.so$'Confirmed by developer.android.com
Cause 2 of 3
abiFilters or ABI splits leave the device's ABI out
1Check
Gradle builds every non-deprecated ABI by default, and abiFilters restricts that set. With ABI splits turned on, Gradle builds one APK per ABI, and a universal APK only when universalApk is true. Installing an ARM split on an x86 device fails the same way.
grep -n -E "abiFilters|abi \{|universalApk|isUniversalApk|include" app/build.gradle app/build.gradle.kts 2>/dev/null
ls app/build/outputs/apk/debug/2Fix
Add the device's ABI to the filter or to the split list, install the split that matches the device, or ask for a universal APK for local testing.
android {
splits {
abi {
isEnable = true
reset()
include("arm64-v8a", "x86_64")
isUniversalApk = true
}
}
}3Verify
Build again and install the APK or split that matches the device.
./gradlew assembleDebug
# the file name has the form module-ABI-variant.apk
adb install app/build/outputs/apk/debug/app-<abi>-debug.apkConfirmed by developer.android.com
Cause 3 of 3
Only 32-bit libraries on a device or emulator that is 64-bit only
1Check
For each 32-bit ABI an app supports, Google requires the matching 64-bit one: arm64-v8a for armeabi-v7a, and x86_64 for x86. Emulator system images are 64-bit only starting with Android 12 (API level 31). A 32-bit-only APK finds no matching folder on them.
zipinfo -1 app/build/outputs/apk/debug/app-debug.apk | grep -E 'lib/(arm64-v8a|x86_64)/'2Fix
Add the 64-bit ABI beside the 32-bit one in the build, and update third-party SDKs that ship only 32-bit binaries.
android {
defaultConfig {
ndk {
abiFilters += listOf("armeabi-v7a", "arm64-v8a")
}
}
}3Verify
The 64-bit folder is present in the APK, and the install succeeds on the 64-bit device.
./gradlew installDebug
zipinfo -1 app/build/outputs/apk/debug/app-debug.apk | grep -E 'lib/(arm64-v8a|x86_64)/'Confirmed by developer.android.com
How do I stop it coming back?
- Ship both the 32-bit and the 64-bit ABI for every CPU family you support, and check the APK with zipinfo or APK Analyzer before release.
- Use abiFilters only to cut size on purpose, and keep an emulator or device for every ABI that remains.
- Update SDKs with native code regularly: an old one may ship only 32-bit binaries.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
Android Studio will not install the app: the device's Android version is too old
INSTALL_FAILED_OLDER_SDK
The system refuses to install an app when its minSdk is higher than the API level of the device or emulator.
3 causes, each with a fixMobile apps
adb install fails with INSTALL_FAILED_INVALID_APK
The install fails on a file named like app-release-unsigned.apk
The device refused the file as an installable APK.
3 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fix