INSTALL_FAILED_NO_MATCHING_ABIS when install apk

Question

I tried to install my app into Android L Preview Intel Atom Virtual Device, it failed with error:

INSTALL_FAILED_NO_MATCHING_ABIS

What does it mean?

Check this link for Android 3.0.1 issue : https://stackoverflow.com/a/49473570/3400991 — Shobhakar Tiwari, Mar 25 '18 at 07:43

score 679 · Accepted Answer · edited Mar 21 '17 at 11:59

679

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.

edited Mar 21 '17 at 11:59

Vasily Kabunov

5,179
12
41
46

answered Jul 04 '14 at 10:26

Hiemanshu Sharma

7,241
1
13
13

I don't understand what changed. I could always use the Intel image (so haxm could make the emulator usable). Now with L I'm forced to use the ARM image? – Daniel Ochoa Oct 06 '14 at 15:10
1

@DanielOchoa Its because they wont to maintain two images for a preview release. When L is officially launched I am sure there will be a Intel x86 image as well. – Hiemanshu Sharma Oct 07 '14 at 07:30
1

How to overcome on this problem. i am using Genymotion Emulater and install gapps and Genymotion-ARM-Translation_v1.1 still m getting this problem. – Prashant Maheshwari Andro Mar 13 '15 at 12:50
4

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. – enl8enmentnow May 13 '15 at 19:23
Check out https://software.intel.com/en-us/blogs/2014/07/03/how-to-set-up-an-ndk-project-to-compile-for-multiple-target-platforms for compiling your native library for Intel-based architecture. – Alexander Pacha May 15 '15 at 15:29
1

Any idea why this won't work on a Nexus 9 running 5.1.1. It works fine on a Sony Xperia Z2 tablet running 4.4.2. Compiled Sdk 21, min 17 abd targeted 22. – Bear Jun 08 '15 at 09:10
1

seems that ARM translator doesn't works on android 5.1, try with 4.3 – Lluís Oct 03 '15 at 22:23
If you are using a version over 4 try this. http://www.techbae.com/download-install-arm-translation-v1-1-zip-genymotion/ – mesutpiskin Mar 23 '17 at 16:14
3

I had this issue while using the Android Studio emulator for a Nexus 5x on my Windows machine. For speed reasons [10x faster] the default is simulating the phone as if it is working with an Intel x86 architecture [Nexus 5x's Snapdragon 808 is actually based on ARM: http://www.tomshardware.com/reviews/lg-g4,4353-2.html ]. I fixed the error entering the AVD manager, selecting the simulated device that was giving me the error and clicking on Edit button where I set up an ARM (armeabi-v7a) architecture. After this change plus emulator reboot the installation went through with no issues – Antonino Apr 10 '18 at 00:48
Is there a way to make an ARM app work on x86 / x86_64 Android emulator if we just have the apk file without the source code? Maybe by decompiling and recompiling the app to the x86 architecture? – baptx Dec 04 '18 at 14:07
I get this error when I deploy from Xamarin/VS. The deployment (signed-apk file) seems to work just fine. I'm running on an Intel machine (Windows 10 enterprise). – Ron Feb 25 '19 at 17:14
I get this error when I try to deploy (to the Emulator) in Release mode only. YET, the signed APK can run no problem on the LG phones I use. SO how would I fix this error? I thought the APKs were architecture neutral in that they run on Android. How would I create an APK for all the different archiectures arouind? – Ron Mar 02 '19 at 00:23
Thank you! I was stuck meddling with environment variables, uninstalling and reinstalling SDKs, changing paths to the SDK for both Android Studio as well as Unity3d. Nothing worked, except changing the architecture from Arm7 to x86(deprecated). Now I have the emulator working for both Unity3d (Build and Run) as well as Android Studio! – pookie Jan 28 '20 at 10:57
Using https://developer.android.com/studio/debug/apk-debugger to debug and review the existing APK could be helpful as well. – dmcgill50 Apr 14 '20 at 13:36
I was trying to run some third party app (didnt have source code for it). Nothing helped, but this sweet little thing https://www.memuplay.com/. Just download, and install the 64 bit version of android (32 is the default and it wont work with that). Then the apk can just be imported and installed – rimes Jul 17 '20 at 12:23
@rimes according to virus Total 28 engines claim that this is malware – yoel halb Nov 18 '20 at 00:04
@yoelhalb I don't think so. I am still using It from time to time, and didn't get any warning. Maybe the hits are false alarm because the software is installing some "internal" stuff. – rimes Nov 18 '20 at 06:11

Asher Garland · Answer 2 · 2020-02-12T00:20:11.573

153

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:

Open your xamarin .sln
Right click your android project
Click properties
Click Android Options
Click the 'Advanced' tab
Under "Supported architectures" make the following checked:
1. armeabi-v7a
2. x86
save
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.

edited Feb 12 '20 at 00:20

answered Jan 31 '17 at 22:59

Asher Garland

4,293
4
23
28

7

That solution worked on Visual Studio 2017 too, for a Xamarin.Android project. – corentinaltepe Jun 03 '17 at 00:53
1

This also worked for me when using an Android WebView App project – JRodd Jan 19 '18 at 19:49
4

It seems on Xamarin, on every new day there is a new, unexpected obstackle preventing me from running my application (which worked yesterday). Since my csproj file is on dropbox, I could check version history, and this property was not in the file yesterday, it was missing altogether. Today, I had to add the x86 option in order to make app run. Why on earth is xamarin or android suddenly using different default values? This is so frustrating! Anyway, thanks to people like you, I can overcome and get on with work. Thanks a lot, and +1 for you! – TMan Feb 03 '18 at 11:25
2

Wish I could upvote more than once... Tested and working on VS 2017 for Mac. – JordiVilaplana Apr 26 '18 at 11:23
For Visual Studio Community 2019 for Mac: 1. Right click on your android project 2. Click Options 3. Click Android Build 4. Advanced – null Mar 31 '20 at 08:31

score 92 · Answer 3 · answered Nov 17 '15 at 16:05

92

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 '15 at 16:05

Driss Bounouar

2,852
28
45

2

Failure [INSTALL_FAILED_NO_MATCHING_ABIS] – abbasalim Aug 03 '16 at 11:41
Didn't work for me and could not find `(yourapp)-x86-debug.apk` file in my project output. – Eido95 Jan 03 '17 at 20:15
I don't necessarily want to split APKs, is that an option? @DrissBounouar – ericn Jan 11 '18 at 07:24
You can use the universal apk, presumably it has both architectures. – Driss Bounouar Jan 12 '18 at 16:33
still facing the same problem – Vikash Parajuli Mar 14 '18 at 07:07

score 61 · Answer 4 · edited Jan 24 '15 at 15:34

61

If you using Genymotion you need Installing ARM Translation and GApps

edited Jan 24 '15 at 15:34

Bill the Lizard

369,957
201
546
842

answered Nov 20 '14 at 07:18

R00We

1,791
17
21

In some APIs that you used,You need add both "ARM Translation Installer v1.1" and "GApps for your Android version". – saneryee Jan 21 '15 at 09:47
4

UPDATE May 28th, 2017: This guide is no longer supported and probably doesn't work. Please don't use it or ask for support anymore. from xda-developers – AndroidCoolestRulest Sep 21 '17 at 18:12
2

You can follow [this link](https://pentester.land/tips-n-tricks/2018/10/19/installing-arm-android-apps-on-genymotion-devices.html) to install ARM Translation – Devansh Maurya Jul 10 '19 at 16:55

IgorGanapolsky · Answer 5 · 2017-03-01T14:07:13.030

43

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]

edited Mar 01 '17 at 14:07

answered Mar 31 '16 at 16:24

IgorGanapolsky

23,124
17
109
132

1

Hi. This made my project build successfully but still it gave me the same error. I am working on mac, genymotion. Also, in general, is this settings that you told are only for the debug version or also for release build? – master_dodo Jun 10 '16 at 19:23
@user3241111 This can be used for both debug and prod. Have you tried to clean your project. Or perhaps invalidate/restart Android Studio? – IgorGanapolsky Jun 10 '16 at 19:37
I've not tried to clean build but I noticed that it didn't create -x86-debug.apk But I'll shorlty try ways- clean and also restarting android studio(It does Synch btw). Also, for build process I am using terminal and not Android Studio. – master_dodo Jun 10 '16 at 19:48
1

@user3241111 If you are using gradlew for command-line terminal builds, then you can still clean your project with gradle. – IgorGanapolsky Jun 10 '16 at 20:08
1

I tried this solution, it worked.. In my project there wasn't any APP_ABI. But I added it accordingly and it build just one apk and it works. http://stackoverflow.com/a/35565901/3241111 – master_dodo Jun 10 '16 at 20:17
How to clean build from command line? Actually, I thought that Android Studio is keeping my android setting in synch so I might not need to clean. I wanted to avoid this process bcoz it takes 10 min to build my project(cocos2d-x library). I've just started to setup this thing. – master_dodo Jun 10 '16 at 20:24
1

Also, I just added enabled gradle daemon and it has paced up the process so much... Anyways, thanks for your support :) – master_dodo Jun 10 '16 at 20:54
In my case if i add above code , it shows Error:Execution failed for task ':app:processArmeabi-v7aDebugResources'. > Cannot invoke method replaceAll() on null object – ashraful Apr 02 '17 at 12:27
@ashraful Perform a clean of your project and reassemble from command-line. Also, make sure you have the latest Gradle tools and build tools in your project. – IgorGanapolsky Apr 03 '17 at 13:07

score 14 · Answer 6 · edited Aug 11 '20 at 06:31

14

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.

edited Aug 11 '20 at 06:31

larsaars

837
1
12
25

answered Sep 14 '18 at 17:14

Saba

570
5
14

7

Thank you so much, you save my day. I dont know why I got: implementation 'org.apache.directory.studio:org.apache.commons.io:2.4' – Pierrick HYMBERT Sep 18 '18 at 17:02

score 13 · Answer 7 · edited Jun 22 '18 at 11:25

13

This solution worked for me. Try this, add following lines in your app's build.gradle file

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

edited Jun 22 '18 at 11:25

saketr64x

46
10

answered Sep 15 '17 at 06:14

vaibhav

184
1
9

score 12 · Answer 8 · answered Sep 07 '16 at 06:16

I know there were lots of answers here, but the TL;DR version is this (If you're using Xamarin Studio):

Right click the Android project in the solution tree
Select Options
Go to Android Build
Go to Advanced tab
Check the architectures you use in your emulator (Probably x86 / armeabi-v7a / armeabi)
Make a kickass app :)

score 10 · Answer 9 · answered Nov 26 '18 at 21:22

10

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 '18 at 21:22

ediBersh

1,025
1
12
17

Thanks. It helped me with Bitcoin J Integration. – Umer Kiani Jan 18 '19 at 15:07
Thanks you so much i am try many solution but this solution works for me for me My issue is for scrypt-1.4.0.jar not install in android Pie version (Nokia 7.1)Device – Sagar Pithiya Feb 01 '19 at 10:08

score 9 · Answer 10 · answered Aug 14 '18 at 22:31

this worked for me ... Android > Gradle Scripts > build.gradle (Module:app) add inside android*

android {
  //   compileSdkVersion 27
     defaultConfig {
        //
     }
     buildTypes {
        //
     }
    // buildToolsVersion '27.0.3'

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

score 7 · Answer 11 · answered Jun 15 '15 at 09:23

7

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 '15 at 09:23

muetzenflo

4,344
3
27
65

1

I am working on mac and probably it's build for x86 virtual device. I tried with genymotion custom tablet also, it didn't work, and gave same error while installing – master_dodo May 09 '16 at 07:26

score 6 · Answer 12 · answered Jun 21 '17 at 20:46

6

Visual Studio mac - you can change the support here:

answered Jun 21 '17 at 20:46

LeRoy

3,437
2
29
38

score 3 · Answer 13 · answered Oct 27 '18 at 00:29

3

In my case, in a xamarin project, in visual studio error removed by selecting properties --> Android Options and check Use Share run Times and Use Fast Deployment, in some cases one of them

answered Oct 27 '18 at 00:29

Saleem Kalro

882
8
11

score 2 · Answer 14 · edited May 23 '17 at 12:18

2

For genymotion on mac, I was getting INSTALL_FAILED_NO_MATCHING_ABIS error while installing my apk.

In my project there wasn't any "APP_ABI" but I added it accordingly and it built just one apk for both architectures but it worked. https://stackoverflow.com/a/35565901/3241111

edited May 23 '17 at 12:18

Community

1
1

answered Jun 10 '16 at 20:22

master_dodo

1,112
1
16
25

Kusal Dissanayake · Answer 15 · 2018-03-27T06:57:30.663

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,

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

score 2 · Answer 16 · answered Nov 15 '18 at 08:27

Basically if you tried Everything above and still you have the same error "Because i am facing this issue before too" then check which .jar or .aar or module you added may be the one library using ndk , and that one is not supporting 8.0 (Oreo)+ , likewise i am using Microsoft SignalR socket Library adding its .jar files and latterly i found out app not installing in Oreo then afterwards i remove that library because currently there is no solution on its git page and i go for another one.

So please check the library you are using and search about it if you eagerly needed that one.

Denis Dmitrienko · Answer 17 · 2020-04-01T09:57:41.387

In general case to find out which library dependency has incompatible ABI,

build an APK file in Android Studio (menu Build > Build Bundle(s)/APK(s) > Build APK(s)) // actual on 01.04.2020
rename APK file, replacing extension "apk" with extension "zip"
unpack zip file to a new folder
go to libs folder
find out which *.jar libraries with incompatible ABIs are there

You may try to upgrade version / remove / replace these libraries to solve INSTALL_FAILED_NO_MATCHING_ABIS when install apk problem

score 2 · Answer 18 · answered Dec 21 '20 at 16:04

this problem is for CPU Architecture and you have some of the abi in the lib folder.

go to build.gradle for your app module and in android, block add this :

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

score 1 · Answer 19 · answered Dec 22 '18 at 05:09

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

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

score 1 · Answer 20 · answered Mar 22 '19 at 06:11

I faced this issue when moved from Android 7(Nougat) to Android 8(Oreo).

I have tried several ways listed above and to my bad luck nothing worked.

So i changed the .apk file to .zip file extracted it and found lib folder with which this file was there /x86_64/darwin/libscrypt.dylib so to remove this i added a code in my build.gradle module below android section (i.e.)

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

Cheers issue solved

score 0 · Answer 21 · answered Jun 18 '18 at 03:01

0

This happened to me. I checked the SDK Manager and it told me the one I was using had a update. I updated it and the problem went away.

answered Jun 18 '18 at 03:01

Barry Fruitman

11,209
10
64
121

score 0 · Answer 22 · answered Nov 13 '18 at 01:46

Quite late, but just ran into this. This is for Xamarin.Android. Make sure that you're not trying to debug in release mode. I get that exact same error if in release mode and attempting to debug. Simply switching from release to debug allowed mine to install properly.

score 0 · Answer 23 · answered Jul 29 '19 at 12:55

0

In my case setting folowing options helpet me out

answered Jul 29 '19 at 12:55

Stefan Michev

3,938
2
32
29

score 0 · Answer 24 · answered Jul 16 '20 at 07:57

0

Somehow, this fix the issue out of no reason.

./gradlew clean assemble and then install the app.

answered Jul 16 '20 at 07:57

Francis Bacon

1,928
1
18
30

score 0 · Answer 25 · answered Sep 15 '20 at 15:58

0

Just in case, this might help someone like me. I had this same issue in Unity 3D. I was attempting to use the emulators from Android Studio. So I enabled Target Architecture->x86 Architecture(although deprecated) in Player Settings and it worked!

answered Sep 15 '20 at 15:58

Sagar Wankhede

112
1
2

INSTALL_FAILED_NO_MATCHING_ABIS when install apk

25 Answers25

Linked

Related