Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

Sadique Hassan•Updated Feb 19, 2025

In this guide, we will be discussing plausible reasons as well as the potential fixes for the “Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]’; Code: ‘1’” error. So without any further ado, let’s get started.

Failure [INSTALL_FAILED_NO_MATCHING_ABIS Failed to extract native libraries, res=-113]

Table of Contents

Reason for Failure [INSTALL_FAILED_NO_MATCHING_ABIS]

This issue is happening because the APK that you are trying to install has native libraries compiled for a different architecture than what your device supports. For example, if your device has an arm64-v8a architecture but you are trying to install an APK that is built for armeabi-v7a, then you’ll be greeted with the aforementioned error.

TIP: The list of available architecture for an Android device is: armeabi-v7a, arm64-v8a, x86, and x86_64.

In short, the reason for INSTALL_FAILED_NO_MATCHING_ABIS is the incompatibility between the CPU architecture of your device and the app in question.

How is it Different From “App not installed as App isn’t compatible with your phone“

There has been a long-standing confusion wherein users tend to link the INSTALL_FAILED_NO_MATCHING_ABIS error with “App not installed as App isn’t compatible with your phone”. So are they one and the same thing? Well, not exactly. The latter issue happens when you are trying to install an app that was built for an older app version [SDK version] but you are trying to install on a newer Android OS whereas the former is due to CPU architecture incompatibility. Moreover, the latter issue could easily be rectified using just a single line of ADB Command! But what about the former? Let’s find out.

App not installed as App isn’t compatible with your phone [Fixed]

Fix Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]’; Code: ‘1’”

You can take four different approaches to address this issue, namely:

The first and obvious fix is to find and download the APK that corresponds to your CPU architecture [which most of you would have already tried by now].
Adjust the APK build option > modify the supported architectures section > add the required architecture.
Ask the developer to create an APK for the architecture that is required by your device.
Ask the dev to create a universal APK that is supported across all the architectures.

Let’s now have a look at each of these fixes in depth. But before that, make sure to re-verify your device’s architecture. You can do the same via a third-party app like CPU Z [go to the System tab and check out the kernel Architecture section]. Do note that “aarch64” and “arm64” are one and the same thing.

FIX 1

Your first course of action is to find an APK that corresponds to your device’s CPU architecture. In this regard, there are quite a few third-party websites, however, we would be going ahead with the APKMirror. If you are also on the same site, then search for the desired app and then head over to the All Variants section. Now refer to the Architecture section and download the app that corresponds to your device.

FIX 2

Next up, try installing the app in question via the –bypass-low-target parameter in the ADB Command and then see if it works for you or not.

FIX 3

If you are using Visual Studio with Xamarin, then refer to the below steps. This tweak works on both Visual Studio 2015 and 2017, including the Mac version [Credit: Asher G on StackOverflow].

Open your Xamarin project solution (.sln) in Visual Studio.
Right-click on your Android project and select Properties.
Navigate to Android Options and select the Advanced tab.
Select your device architecture under Supported Architectures.
Finally, save the changes and rebuild the project (press F5).
Then install the APK and you should face no issues now.

For projects using Gradle, you’ll have to modify the build.gradle file and add the required architecture as follows:

splits {
abi {
enable true
reset()
include 'x86', 'armeabi-v7a','arm64'
universalApk true
}
}

FIX 4

If you are not well versed in coding, then you can request the app developer to release their app which is compatible with your device’s CPU architecture. However, it completely depends on the developer’s willingness to do so, so try out your convincing power and see if it works out!

Official Documentations

You can refer to some official documentation on this matter here, here, and here. Likewise, you can also share these resources with the app developers [though most of them might already be aware of these technicalities].

That’s it. This was all from this guide regarding the reasons and fixes for “Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]’; Code: ‘1’” error. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.

Tags:

AndroidError Fix