Fix lỗi your device do not support memu play

adb install [yourapp]-x86-debug.apk

1 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.

answered Jul 4, 2014 at 10:26

Hiemanshu SharmaHiemanshu Sharma

7,7321 gold badge16 silver badges13 bronze badges

18

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

Asher G.Asher G.

4,9135 gold badges28 silver badges30 bronze badges

5

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

Driss BounouarDriss Bounouar

3,2122 gold badges32 silver badges50 bronze badges

5

answered Nov 20, 2014 at 7:18

R00WeR00We

1,95118 silver badges21 bronze badges

3

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

IgorGanapolskyIgorGanapolsky

26.4k23 gold badges117 silver badges147 bronze badges

10

On Android 8:

apache.commons.io:2.4

gives INSTALL_FAILED_NO_MATCHING_ABIS, try to change it to

adb install [yourapp]-x86-debug.apk

2 and it will work.

answered Sep 14, 2018 at 17:14

SabaSaba

1,34316 silver badges20 bronze badges

1

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
    }
}

answered Sep 15, 2017 at 6:14

vaibhavvaibhav

3122 silver badges10 bronze badges

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

1. Right click the Android project in the solution tree
2. Select

   adb install [yourapp]-x86-debug.apk

   3
3. Go to

   adb install [yourapp]-x86-debug.apk

   4
4. Go to

   adb install [yourapp]-x86-debug.apk

   5 tab
5. Check the architectures you use in your emulator [Probably

   adb install [yourapp]-x86-debug.apk

   6 /

   adb install [yourapp]-x86-debug.apk

   7 /

   adb install [yourapp]-x86-debug.apk

   8]
6. Make a kickass app :]

answered Sep 7, 2016 at 6:16

Jonathan PerryJonathan Perry

2,9633 gold badges44 silver badges51 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

ediBershediBersh

1,1351 gold badge12 silver badges19 bronze badges

3

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
               }
    }
 }

answered Aug 14, 2018 at 22:31

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

muetzenflomuetzenflo

5,6254 gold badges42 silver badges84 bronze badges

1

Visual Studio mac - you can change the support here:

answered Jun 21, 2017 at 20:46

LeRoyLeRoy

4,2552 gold badges37 silver badges46 bronze badges

this problem is for CPU Architecture and you have some of the

adb install [yourapp]-x86-debug.apk

9 in the

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

0 folder.

go to

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

1 for your

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

2 and in

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

3, block add this :

  splits {
            abi {
                enable true
                reset[]
                include 'x86', 'armeabi-v7a'
                universalApk true
            }
        }

answered Dec 21, 2020 at 16:04

Sana EbadiSana Ebadi

6,8162 gold badges46 silver badges45 bronze badges

In my case[Windows 10, Flutter, Android Studio], I simply created a new emulator device in Android Studio. This time, I have chosen x86_64 ABI instead of only x86. It solved my issue. My emulator devices are shown in the screenshot below.

answered Sep 27, 2021 at 22:15

2

Hi if you are using this library;

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

Replace it with:

implementation 'commons-io:commons-io:2.6'

And the problem will be fixed.

answered Jul 10, 2022 at 23:10

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.

 armeabi;armeabi-v7a;x86;x86_64;arm64-v8a

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

1

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, 2018 at 0:29

Saleem KalroSaleem Kalro

1,0569 silver badges12 bronze badges

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

1. Go to //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

FidelFidel

7,13711 gold badges59 silver badges82 bronze badges

0

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. //stackoverflow.com/a/35565901/3241111

answered Jun 10, 2016 at 20:22

master_dodomaster_dodo

1,2733 gold badges21 silver badges31 bronze badges

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.

answered Nov 15, 2018 at 8:27

Sumit KumarSumit Kumar

6431 gold badge8 silver badges19 bronze badges

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

answered Mar 13, 2020 at 9:37

Denis DmitrienkoDenis Dmitrienko

1,5812 gold badges16 silver badges27 bronze badges

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

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

4[although deprecated] in Player Settings and it worked!

answered Sep 15, 2020 at 15:58

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.]

adb install [yourapp]-x86-debug.apk

0

Cheers issue solved

answered Mar 22, 2019 at 6:11

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, 2018 at 3:01

Barry FruitmanBarry Fruitman

12.3k13 gold badges73 silver badges135 bronze badges

Quite late, but just ran into this. This is for

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

5. 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.