Ошибка install failed no matching abis - Ремонт и установка крупной бытовой техники

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?

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.

answered Jul 4, 2014 at 10:26

Hiemanshu SharmaHiemanshu Sharma

7,6421 gold badge16 silver badges13 bronze badges

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.

answered Jan 31, 2017 at 22:59

Asher GarlandAsher Garland

4,8835 gold badges27 silver badges29 bronze badges

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,1722 gold badges32 silver badges48 bronze badges

answered Nov 20, 2014 at 7:18

R00WeR00We

1,93118 silver badges21 bronze badges

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.1k23 gold badges116 silver badges147 bronze badges

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

SabaSaba

1,16412 silver badges19 bronze badges

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

3022 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):

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

answered Sep 7, 2016 at 6:16

Jonathan PerryJonathan Perry

2,9332 gold badges43 silver badges50 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,1251 gold badge12 silver badges19 bronze badges

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

enter image description here

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,6134 gold badges41 silver badges82 bronze badges

Visual Studio mac — you can change the support here:

enter image description here

answered Jun 21, 2017 at 20:46

LeRoyLeRoy

3,8642 gold badges34 silver badges43 bronze badges

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

answered Dec 21, 2020 at 16:04

Sana EbadiSana Ebadi

6,5822 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,

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

answered Mar 22, 2018 at 5:58

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 enter image description here

answered Oct 27, 2018 at 0:29

Saleem KalroSaleem Kalro

1,0469 silver badges12 bronze badges

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

answered Dec 22, 2018 at 5:09

FidelFidel

6,92711 gold badges53 silver badges80 bronze badges

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

answered Jun 10, 2016 at 20:22

master_dodomaster_dodo

1,1753 gold badges19 silver badges30 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,5122 gold badges16 silver badges26 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 Target Architecture->x86 Architecture(although deprecated) in Player Settings and it worked!

answered Sep 15, 2020 at 15:58

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.
New and Old Emulator Devices

answered Sep 27, 2021 at 22:15

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

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

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.2k13 gold badges72 silver badges131 bronze badges

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.

answered Nov 13, 2018 at 1:46

NieminenNieminen

1,2642 gold badges13 silver badges31 bronze badges

In my case setting folowing options helpet me out

enter image description here

answered Jul 29, 2019 at 12:55

Stefan MichevStefan Michev

4,7773 gold badges35 silver badges30 bronze badges

Somehow, this fix the issue out of no reason.

./gradlew clean assemble and then install the app.

answered Jul 16, 2020 at 7:57

Francis BaconFrancis Bacon

3,9101 gold badge34 silver badges47 bronze badges

Источник

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?

asked Jul 4, 2014 at 10:17

answered Jul 4, 2014 at 10:26

Hiemanshu SharmaHiemanshu Sharma

7,6421 gold badge16 silver badges13 bronze badges

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.

answered Jan 31, 2017 at 22:59

Asher GarlandAsher Garland

4,8835 gold badges27 silver badges29 bronze badges

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

adb install (yourapp)-x86-debug.apk

answered Nov 17, 2015 at 16:05

Driss BounouarDriss Bounouar

3,1722 gold badges32 silver badges48 bronze badges

answered Nov 20, 2014 at 7:18

R00WeR00We

1,93118 silver badges21 bronze badges

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.1k23 gold badges116 silver badges147 bronze badges

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

SabaSaba

1,16412 silver badges19 bronze badges

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

3022 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):

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

answered Sep 7, 2016 at 6:16

Jonathan PerryJonathan Perry

2,9332 gold badges43 silver badges50 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,1251 gold badge12 silver badges19 bronze badges

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

enter image description here

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,6134 gold badges41 silver badges82 bronze badges

Visual Studio mac — you can change the support here:

enter image description here

answered Jun 21, 2017 at 20:46

LeRoyLeRoy

3,8642 gold badges34 silver badges43 bronze badges

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

answered Dec 21, 2020 at 16:04

Sana EbadiSana Ebadi

6,5822 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,

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

answered Mar 22, 2018 at 5:58

answered Oct 27, 2018 at 0:29

Saleem KalroSaleem Kalro

1,0469 silver badges12 bronze badges

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

answered Dec 22, 2018 at 5:09

FidelFidel

6,92711 gold badges53 silver badges80 bronze badges

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

answered Jun 10, 2016 at 20:22

master_dodomaster_dodo

1,1753 gold badges19 silver badges30 bronze badges

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,5122 gold badges16 silver badges26 bronze badges

answered Sep 15, 2020 at 15:58

answered Sep 27, 2021 at 22:15

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

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.

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

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.2k13 gold badges72 silver badges131 bronze badges

answered Nov 13, 2018 at 1:46

NieminenNieminen

1,2642 gold badges13 silver badges31 bronze badges

In my case setting folowing options helpet me out

enter image description here

answered Jul 29, 2019 at 12:55

Stefan MichevStefan Michev

4,7773 gold badges35 silver badges30 bronze badges

Somehow, this fix the issue out of no reason.

./gradlew clean assemble and then install the app.

answered Jul 16, 2020 at 7:57

Francis BaconFrancis Bacon

3,9101 gold badge34 silver badges47 bronze badges

Источник

When installing my app to Android L preview it fails with error:

INSTALL_FAILED_NO_MATCHING_ABIS.

My app uses arm only library, features that uses library is disabled on x86. It works perfectly before Android L, but now i can’t even install it. How to disable this error for my app?

asked Jul 15, 2014 at 6:31

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

kenorb

154k86 gold badges676 silver badges742 bronze badges

answered Oct 16, 2015 at 20:19

PatrickPatrick

2913 silver badges2 bronze badges

I think the thread starter wants build a single APK with an optional native libary, which will only be loaded on ARM devices. This seems impossible at the moment (only using splits/multi apk). I’m facing the same issue and have created a bug report.

answered Jan 22, 2016 at 9:56

jbxbergdevjbxbergdev

8501 gold badge10 silver badges23 bronze badges

This problem also come with when working with unity also. The problem is your app uses ARM architecture and the device or emulator that you are trying to install the app support otherwise such as x86. Try installing it on ARM emulator. Hope that solves the problem.

answered Dec 25, 2014 at 11:16

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

You can find your answer in
INSTALL_FAILED_NO_MATCHING_ABIS when install apk

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.

answered Jun 17, 2015 at 21:03

FredFred

3,3554 gold badges36 silver badges57 bronze badges

Источник

21 ответ

INSTALL_FAILED_NO_MATCHING_ABIS — это когда вы пытаетесь установить приложение с родными библиотеками, и у него нет собственной библиотеки для вашей архитектуры процессора. Например, если вы скомпилировали приложение для armv7 и пытаетесь установить его на эмулятор, который использует архитектуру Intel, то это не сработает.

Hiemanshu Sharma
04 июль 2014, в 11:58

INSTALL_FAILED_NO_MATCHING_ABIS — это когда вы пытаетесь установить приложение с родными библиотеками, и у него нет собственной библиотеки для вашей архитектуры процессора. Например, если вы скомпилировали приложение для armv7 и пытаетесь установить его на эмулятор, который использует архитектуру Intel, то это не сработает.

Использование Xamarin на Visual Studio 2015. Исправить эту проблему:

Откройте свой xamarin.sln
Щелкните правой кнопкой мыши ваш проект Android
Свойства кликов
Нажмите «Настройки Android».
Перейдите на вкладку «Дополнительно».
В разделе «Поддерживаемые архитектуры» выполните следующие проверки:
1. armeabi-v7a
2. x86
спасти
F5 (построить)

Изменить. Сообщается, что это решение работает и на Visual Studio 2017.

Редактировать 2: Сообщается, что это решение работает и в Visual Studio 2017 для Mac.

Asher Garland
31 янв. 2017, в 23:40

Я отправляю ответ из другого потока, потому что это хорошо работает для меня, трюк заключается в том, чтобы добавить поддержку для обеих архитектур:

Проводя это, потому что я не мог найти прямой ответ и должен был посмотреть несколько разных сообщений, чтобы получить то, что я хотел сделать…

Я смог использовать эмулятор x86 Accelerated (HAXM), просто добавив его в свой модуль build.gradle script Inside android {} block:

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

Запустить (построить)… Теперь в вашей выходной папке будет файл (yourapp) -x86-debug.apk. Я уверен, что есть способ автоматизировать установку после запуска, но я просто запускаю свой предпочтительный эмулятор HAXM и использую командную строку:

adb install (yourapp)-x86-debug.apk

Driss Bounouar
17 нояб. 2015, в 17:07

Это действительно странная ошибка, которая может быть вызвана мультисайсом вашего приложения. Чтобы обойти это, используйте следующий блок в своем приложении build.gradle:

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

IgorGanapolsky
31 март 2016, в 18:12

Я знаю, что здесь было много ответов, но версия TL; DR — это (если вы используете Xamarin Studio):

Щелкните правой кнопкой мыши проект Android в дереве решений
Выберите Options
Перейдите к Android Build
Перейдите на вкладку Advanced
Проверьте архитектуры, которые вы используете в своем эмуляторе (возможно x86/armeabi-v7a/armeabi)
Сделайте приложение для kickass:)

Jonathan Perry
07 сен. 2016, в 06:42

Комментарий @enl8enmentnow должен быть ответом, чтобы исправить проблему с помощью genymotion:

Если у вас есть эта проблема в Genymotion даже при использовании транслятора ARM, это происходит из-за того, что вы создаете виртуальное устройство x86, такое как Google Nexus 10. Вместо этого выберите виртуальное устройство ARM, например, одну из пользовательских таблеток.

muetzenflo
15 июнь 2015, в 10:47

Это решение сработало для меня. Попробуйте это, добавьте следующие строки в файл build.gradle приложения.

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

vaibhav
15 сен. 2017, в 07:11

Visual Studio mac — вы можете изменить поддержку здесь:

LeRoy
21 июнь 2017, в 22:45

INSTALL_FAILED_NO_MATCHING_ABIS означает, что архитектура не соответствует. Если вы используете Android Studio на Mac (который обычно использует Apple ARM), тогда вам нужно установить CPU/ABI Android Virtual Device на «arm» или «armeabi-v7a». Если, однако, вы используете Android Studio на ПК (который обычно использует чип Intel, затем установите значение «x86» или «x86_64».

TomV
14 дек. 2015, в 19:55

На Android 8:

apache.commons.io:2.4

он дает INSTALL_FAILED_NO_MATCHING_ABIS, попробуйте изменить его на 2.5 или 2.6, и он будет работать или комментировать его.

Saba Jafarzadeh
14 сен. 2018, в 18:12

В сообществе сообщества Visual Studio 2017 иногда выбор поддерживаемых ABI из Android Options не работает.

В этом случае убедитесь, что.csproj имеет следующую строку и не содержит повторяющихся строк в тех же конфигурациях сборки.

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

Чтобы редактировать,

Выгрузите свой Android-проект
Щелкните правой кнопкой мыши и выберите «Редактировать проект»…
Убедитесь, что указанная выше строка имеет только один раз в конфигурации сборки
Сохранить
Щелкните правой кнопкой мыши на своем проекте android и перезагрузите

Kusal Dissanayake
22 март 2018, в 07:29

У меня была эта проблема, используя библиотеку bitcoinJ (org.bitcoinj: bitcoinj-core: 0.14.7), добавленную в build.gradle (в модуле app) варианты упаковки внутри области android. это помогло мне.

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

ediBersh
26 нояб. 2018, в 22:31

В моем случае, в проекте xamarin, при удалении визуальной студия удалены, выбрав свойства → Настройки Android и установите флажок Использовать время выполнения и используйте быстрое развертывание, в некоторых случаях один из них

saleem kalro
27 окт. 2018, в 01:06

это сработало для меня… Android> Gradle Scripts> build.gradle(Module: app) добавить внутри android *

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

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

user8554744
14 авг. 2018, в 23:31

В моем случае мне нужно было скачать версию приложения для x86.

Перейти на https://www.apkmirror.com/
Поиск приложения
Выберите первый в списке
Посмотрите на верхнюю часть страницы, где находится [Название компании]> [Имя приложения]> [Номер версии]
Нажмите на название приложения
Нажмите «Все варианты»
Список должен содержать вариант x86 для загрузки

Fidel
22 дек. 2018, в 06:34

В основном, если вы попробовали все выше и по-прежнему у вас та же ошибка «Потому что я тоже сталкивался с этой проблемой раньше», то проверьте, какой .jar или .aar или модуль, который вы добавили, может быть той библиотекой, использующей ndk, и которая не поддерживает 8.0 (Oreo) +, также я использую библиотеку сокетов Microsoft SignalR, добавляя свои файлы .jar, и недавно я обнаружил, что приложение не устанавливается в Oreo, а затем я удаляю эту библиотеку, потому что в настоящее время на ее странице git нет решения, и я перехожу к другой.,

Поэтому, пожалуйста, проверьте библиотеку, которую вы используете, и поищите ее, если она вам очень нужна.

Sumit Kumar
15 нояб. 2018, в 09:11

Довольно поздно, но просто наткнулся на это. Это для Xamarin.Android. Убедитесь, что вы не пытаетесь отлаживать в режиме выпуска. Я получаю точно такую же ошибку, если в режиме выпуска и пытаюсь отладить. Простое переключение с релиза на отладку позволило моему установить правильно.

Nieminen
13 нояб. 2018, в 03:13

Это случилось со мной. Я проверил диспетчер SDK, и он сказал мне, что у меня было обновление. Я обновил его, и проблема исчезла.

Barry Fruitman
18 июнь 2018, в 04:34

Существует простой способ:

Отключите подключенное устройство
Закройте Android Studio
Перезапустите Android Studio
Подключите устройство с помощью USB-кабеля
Нажмите кнопку «Запустить» и перейдите на кофе-брейк

HA S
15 март 2018, в 02:23

Ещё вопросы

0Странная проблема со смещенной вершиной в jquery
0PHP массив не работает правильно
0PHP Назначение переменных для нескольких строк динамической формы
1Изменение состояния элементов управления ленты Office из других мест приложения в VSTO
1Почему для запуска функции требуется первый двойной щелчок, а затем один щелчок?
0Как загрузить jQuery перед кодом CSS?
0JQuery 1.9.1 DatePicker установить опцию даты
1ждать процесса в процессе
0Вывести кортеж в списке STL
1Как мне ждать, пока мои данные не будут получены из Firebase? [Дубликат]
0Разве этот код jQuery не должен возвращать все входные данные внутри # product-create-2?
1Возврат нужного значения в классе — Java
0Проверьте, отрицательно ли значение более чем в 5 раз, и отметьте их
0Формат IP-адреса в HTML
1C # заблокирован функционирует как механизм блокировки?
0Библиотека разметки каскадных сеток
1Как исправить ошибку Layoutinflator not found?
0Обработчики событий не запускаются
0как отправить почту на wamp сервер?
1добавление пути к файлу в Eclipse
0Найти высоту элемента, содержащего текст
1Проблемы с установкой opencv в Docker-контейнере с помощью pip
0PHP Regexp для получения переменной = «значение» из строки
1Ударьте или пропустите морфологию в python, чтобы найти структуры в изображениях, не дает требуемых результатов
1Запись эквивалентного кода на Паскале в код C #
1Как я могу избежать нарушения Open Closed с параметрами метода?
1Как я могу использовать строку из XML для строковой переменной в C #?
1Какой макет в настоящее время используется Пейзаж или Портрет?
0(PDO) Сбор конкретных данных из идентификатора
0Как разместить 4 изменяемых размера div в горизонтальном расположении?
1Как контролировать отображение окон tkinter Toplevel?
1Получить статус погоды нескольких мест внутри для петли Android
1Отсутствие практического понимания использования Play + Scala против JavaScript
0Ошибки включения Android NDK с помощью cURL
0Доступ к HTML внутри холста
0Динамическая страница в угловом маршруте
0Преобразование прототипа в JQuery — застрял с class.create и classname.prototype
0Изменить текст и HTML, используя jquery
0Невозможно правильно проверить неверный ввод и принять правильные значения диапазона с C ++
0Как я могу использовать jQuery для обновления поля в моей модели рельсов?
1Как очистить анимацию добавления / удаления панели действий?
0Событие внешнего клика для приостановки запроса аудиоплеера
0почему это JQuery не добавляет правильные значения в моей БД
0Использование MySQL REGEX для сопоставления повторяющихся номеров в телефонных номерах
1Array picturebox событие click в c #
1Python — sklearn.MLPClassifier: Как получить выходные данные первого скрытого слоя
1Метод класса не находит данный аргумент
0Переход на другую страницу (через HTML5, CSS3 и JS) в iPad по Swipe (с анимацией слайдов)
1как исправить E / RecyclerView: адаптер не подключен; проблема с пропуском макета

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

nitishk72 opened this issue

Apr 24, 2019

· 23 comments

Comments

When I am trying to install the app in debug mode it works fine but when I try to do the same in Release mode, I get an error. I did lots of googling and none of the solutions works for me.

F:pathtoflutterproject>flutter doctor -v
[√] Flutter (Channel stable, v1.2.1, on Microsoft Windows [Version 10.0.17134.706], locale en-IN)
    • Flutter version 1.2.1 at C:flutter
    • Framework revision 8661d8aecd (10 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:Usersnitishk72AppDataLocalAndroidsdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:Program FilesAndroidAndroid Studiojrebinjava
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)
    • All Android licenses accepted.

[√] Android Studio (version 3.1)
    • Android Studio at C:Program FilesAndroidAndroid Studio
    • Flutter plugin version 27.1.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[√] VS Code (version 1.33.1)
    • VS Code at C:Usersnitishk72AppDataLocalProgramsMicrosoft VS Code
    • Flutter extension version 2.25.1

[√] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!

tempsnip

Edit Android/app/build.gradle

Add the following code in Android block

ndk {
            abiFilters 'armeabi-v7a', 'x86', 'armeabi'
        }

Create a file at Android/app/gradle.properties, put following code in it

target-platform=android-arm

d-apps, fengqiangboy, and Cynnexis reacted with thumbs up emoji
YeFei572, bartektartanus, nezz0746, mmtolsma, Viacheslav-Romanov, Cheas, thereis, bartekpacia, jlund24, bkkterje, and 12 more reacted with thumbs down emoji

when running flutter build apk, it will use --target-platform=android-arm as default which will generate apk for arm32 architecture
you can see more options for --target-platform by running flutter build apk -h where only arm and arm64 are available

AFAIK currently Flutter cannot build apk for x86 architecture
but you can still run debug on simulator, which is x86
related to #9253

Edit Android/app/build.gradle

Add the following code in Android block
ndk {
            abiFilters 'armeabi-v7a', 'x86', 'armeabi'
        }
Create a file at Android/app/gradle.properties, put following code in it
target-platform=android-arm

I was having this error when I was trying to test my app in avd in debug mode. Following this steps it’s working now.

Edit Android/app/build.gradle

Add the following code in Android block
ndk {
            abiFilters 'armeabi-v7a', 'x86', 'armeabi'
        }
Create a file at Android/app/gradle.properties, put following code in it
target-platform=android-arm
I was having this error when I was trying to test my app in avd in debug mode. Following this steps it’s working now.

it’s work ,good boy.but I don’t know why?

Edit Android/app/build.gradle

Add the following code in Android block
ndk {
            abiFilters 'armeabi-v7a', 'x86', 'armeabi'
        }
Create a file at Android/app/gradle.properties, put following code in it
target-platform=android-arm
I was having this error when I was trying to test my app in avd in debug mode. Following this steps it’s working now.
it’s work ,good boy.but I don’t know why?

Because flutter can not package both arm32 and arm64, so, we force gradle to use arm32 package, and arm32 file can run on both arm32 device and arm64 device.

Facing a same issue,

Generating apk with flutter build apk

and when i try to install that apk with flutter install

I got following error.

Error: ADB exited with exit code 1
Performing Streamed Install

adb: failed to install /build/app/outputs/apk/app.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
Install failed

@DevarshRanpara @Xgamefactory can you post flutter doctor -v outputs?
just checking what architecture is your deployment target

FYI google play store enforce appbundle for everyone on their store, so you might want to try building appbundle instead

I don’t know the exact solution and still, no developer came with the exact solution.
So, the best solution is to reinstall the flutter and get rid of this problem.

Wait for Flutter team to come with exact solution

Same here, only release version!

Tried proposed solution without success. +1 from my side.

My Android Emulator abi architecture is x86.
So, I tried to compile with x86 option.

But I got this error.

Flutter version

Hi @nitishk72
if you are still experiencing this issue with the latest stable version of flutter
please provide your flutter doctor -v ,
your flutter run --verbose
and a reproducible minimal code sample
or the steps to reproduce the problem.
Thank you

LongDirtyAnimAlf

added a commit
to jmpessoa/lazandroidmodulewizard
that referenced
this issue

Feb 24, 2020

enutake

added a commit
to enutake/flutter_app
that referenced
this issue

Feb 25, 2020

After adding below in android/app/build.gradle and run a command flutter run --flavor development, I was able to solve this issue.
You might want to check this article regarding on flavoring flutter
https://medium.com/@salvatoregiordanoo/flavoring-flutter-392aaa875f36

flavorDimensions "flutter"

    productFlavors {
        development {
            dimension "flutter"
            applicationIdSuffix ".dev"
            versionNameSuffix "-dev"
        }
        production {
            dimension "flutter"
        }
    }

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don’t hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

What resolved the issue for me: I went on Android Studio and when creating a new Virtual Device I went on x86 Images and selected an image x86_64 and used this one to create my devices.

sysImage

Try flutter clean and build it again

in my case, run command in your terminal «flutter clean» its great working……
may help in same case. thx

I experienced this too.
Then I

uninstalled android studio
removed ~/Android
Removed ~/.android
Reinstalled android-studio
reinstalled virtual devices
Then everything was fine

hey I solved it

run flutter clean
run flutter build apk
then run flutter install

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

github-actions
bot

locked as resolved and limited conversation to collaborators

Aug 2, 2021

Источник