Ошибка install failed no matching abis

asked Jul 4, 2014 at 10:17

INSTALL_FAILED_NO_MATCHING_ABIS is when you are trying to install an app that has native libraries and it doesn’t have a native library for your cpu architecture. For example if you compiled an app for armv7 and are trying to install it on an emulator that uses the Intel architecture instead it will not work.

Using Xamarin on Visual Studio 2015.
Fix this issue by:

1. Open your xamarin .sln
2. Right click your android project
3. Click properties
4. Click Android Options
5. Click the ‘Advanced’ tab

6. Under «Supported architectures» make the following checked:

   1. armeabi-v7a
   2. x86

7. save

8. F5 (build)

Edit: This solution has been reported as working on Visual Studio 2017 as well.

Edit 2: This solution has been reported as working on Visual Studio 2017 for Mac as well.

answered Jan 31, 2017 at 22:59

I’m posting an answer from another thread because it’s what worked well for me, the trick is to add support for both architectures :

Posting this because I could not find a direct answer and had to look at a couple of different posts to get what I wanted done…

I was able to use the x86 Accelerated (HAXM) emulator by simply adding this to my Module’s build.gradle script Inside android{} block:

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

Run (build)… Now there will be a (yourapp)-x86-debug.apk in your output folder. I’m sure there’s a way to automate installing upon Run but I just start my preferred HAXM emulator and use command line:

adb install (yourapp)-x86-debug.apk

answered Nov 17, 2015 at 16:05

answered Nov 20, 2014 at 7:18

This is indeed a strange error that can be caused by multidexing your app. To get around it, use the following block in your app’s build.gradle file:

android {
  splits {
    abi {
        enable true
        reset()
        include 'x86', 'armeabi-v7a'
        universalApk true
    }
  }
  ...[rest of your gradle script]

answered Mar 31, 2016 at 16:24

On Android 8:

apache.commons.io:2.4

gives INSTALL_FAILED_NO_MATCHING_ABIS, try to change it to implementation 'commons-io:commons-io:2.6' and it will work.

answered Sep 14, 2018 at 17:14

answered Sep 15, 2017 at 6:14

Jonathan PerryJonathan Perry

2,9232 gold badges43 silver badges49 bronze badges

i had this problem using bitcoinJ library (org.bitcoinj:bitcoinj-core:0.14.7)
added to build.gradle(in module app) a packaging options inside the android scope.
it helped me.

android {
...
    packagingOptions {
        exclude 'lib/x86_64/darwin/libscrypt.dylib'
        exclude 'lib/x86_64/freebsd/libscrypt.so'
        exclude 'lib/x86_64/linux/libscrypt.so'
    }
}

answered Nov 26, 2018 at 21:22

The comment of @enl8enmentnow should be an answer to fix the problem using genymotion:

If you have this problem on Genymotion even when using the ARM translator it is because you are creating an x86 virtual device like the Google Nexus 10. Pick an ARM virtual device instead, like one of the Custom Tablets.

answered Jun 15, 2015 at 9:23

LeRoyLeRoy

3,8642 gold badges34 silver badges43 bronze badges

Sana EbadiSana Ebadi

6,5622 gold badges43 silver badges43 bronze badges

In the visual studio community edition 2017, sometimes the selection of Supported ABIs from Android Options wont work.

In that case please verify that the .csproj has the following line and no duplicate lines in the same build configurations.

 <AndroidSupportedAbis>armeabi;armeabi-v7a;x86;x86_64;arm64-v8a</AndroidSupportedAbis>

In order to edit,

1. Unload your Android Project
2. Right click and select Edit Project …
3. Make sure you have the above line only one time in a build configuration
4. Save
5. Right click on your android project and Reload

answered Mar 22, 2018 at 5:58

Saleem KalroSaleem Kalro

1,0469 silver badges12 bronze badges

In my case, I needed to download the x86 version of the application.

1. Go to https://www.apkmirror.com/
2. Search for the app
3. Select the first one in the list
4. Look at the top of the page, where is has [Company Name] > [Application Name] > [Version Number]
5. Click the Application Name
6. Click ‘All Variants’
7. The list should contain an x86 variant to download

answered Dec 22, 2018 at 5:09

answered Jun 10, 2016 at 20:22

Sumit KumarSumit Kumar

6431 gold badge8 silver badges19 bronze badges

Denis DmitrienkoDenis Dmitrienko

1,5022 gold badges15 silver badges26 bronze badges

answered Sep 27, 2021 at 22:15

Barry FruitmanBarry Fruitman

12.2k13 gold badges72 silver badges131 bronze badges

NieminenNieminen

1,2642 gold badges13 silver badges31 bronze badges

Stefan MichevStefan Michev

4,7773 gold badges35 silver badges30 bronze badges

Francis BaconFrancis Bacon

3,8901 gold badge34 silver badges47 bronze badges

asked Apr 4, 2016 at 22:45

July 25, 2019 :

I was facing this issue in Android Studio 3.0.1 :

After checking lots of posts, here is Fix which works:

Go to module build.gradle and within Android block add this script:

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

Simple Solution. Feel free to comment. Thanks.

answered Mar 25, 2018 at 7:42

I faced same problem in emulator, but I solved it like this:

Create new emulator with x86_64 system image(ABI)

select device

select x86_64

That’s it.

This error indicates the system(Device) not capable for run the application.

I hope this is helpful to someone.

answered Jun 13, 2017 at 9:00

13 September 2018
It worked for me when add more types and set universalApk with false to reduce apk size

splits {
    abi {
        enable true
        reset()
        include 'x86', 'x86_64', 'armeabi', 'armeabi-v7a', 'mips', 'mips64', 'arm64-v8a'
        universalApk false
    }
}

If you got this error when working with your flutter project, you can add the following code in the module build.gradle and within Android block and then in the defaultConfig block. This error happened when I was trying to make a flutter apk build.

android{
    ...
    defaultConfig{
        ...
        //Add this ndk block of code to your build.gradle
        ndk {
            abiFilters 'armeabi-v7a', 'x86', 'armeabi'
        }
    }
}

answered May 10, 2020 at 17:19

GultekinGultekin

1191 silver badge3 bronze badges

This is caused by a gradle dependency on some out-of-date thing which causes the error. Remove gradle dependencies until the error stops appearing. For me, it was:

implementation 'org.apache.directory.studio:org.apache.commons.io:2.4'

This line needed to be updated to a newer version such as:

api group: 'commons-io', name: 'commons-io', version: '2.6'

answered Aug 3, 2020 at 1:14

After some time i investigate and understand that path were located my libs is right. I just need to add folders for different architectures:

• ARM EABI v7a System Image

• Intel x86 Atom System Image

• MIPS System Image

• Google APIs

answered Apr 15, 2016 at 10:02

Ratul DoleyRatul Doley

4891 gold badge6 silver badges12 bronze badges

BrandonBrandon

1,3811 gold badge15 silver badges25 bronze badges

Make the splits depend on the same list of abis as the external build. Single source of truth.

android {
// ...
defaultConfig {
// ...
    externalNativeBuild {
        cmake {
            cppFlags "-std=c++17"
            abiFilters 'x86', 'armeabi-v7a', 'x86_64'
        }
    }
} //defaultConfig

splits {
    abi {
        enable true
        reset()
        include defaultConfig.externalNativeBuild.getCmake().getAbiFilters().toListString()
        universalApk true
    }
}
} //android

answered Nov 14, 2019 at 13:57

Posting this because I could not find a direct answer and had to look at a couple of different posts to get what I wanted done…

I was able to use the x86 Accelerated (HAXM) emulator by simply adding this to my Module’s build.gradle script Inside android{} block:

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

Run (build)… Now there will be a (yourapp)-x86-debug.apk in your output folder. I’m sure there’s a way to automate installing upon Run but I just start my preferred HAXM emulator and use command line:

adb install (yourapp)-x86-debug.apk

answered Jan 22, 2016 at 9:56

In your application.mk, try to add x86 at

APP_ABI := armeabi-v7a

and it should be look like this

APP_ABI := armeabi-v7a x86

answered Feb 22, 2016 at 23:23

answered Jun 17, 2015 at 21:03

github-actions
bot

locked as resolved and limited conversation to collaborators

Aug 2, 2021