Obsolete
Status Update
No update yet.
Comments
xh...@novetys.com
Thanks.
Here are two:
me.neavo:vitamio:4.2.2 -https://bintray.com/bintray/jcenter/me.neavo:vitamio/view/files/me/neavo/vitamio/4.2.2com.snappydb:snappydb-lib:0.5.0
-https://bintray.com/bintray/jcenter/com.snappydb:snappydb-lib/view/files/com/snappydb/snappydb-lib/0.5.0
this issue can also appear with local libs and projects containing native libs.
If you intend to treat this as an error, note there are still valid use cases where a developer may have a different set of libs for different architectures (for example neon and non-neon versions of native libraries only for arm architectures, totally different implementations for each architectures that provide more or less features, etc).
Here are two:
me.neavo:vitamio:4.2.2 -
-
this issue can also appear with local libs and projects containing native libs.
If you intend to treat this as an error, note there are still valid use cases where a developer may have a different set of libs for different architectures (for example neon and non-neon versions of native libraries only for arm architectures, totally different implementations for each architectures that provide more or less features, etc).
tn...@google.com
Good point, so yeah it should probably be a lint warning rather than a build system error then.
ch...@google.com
Thank you for submitting this issue. It was last modified over a year ago and did not generate a high star count. We have made a large number of improvements in the last year which hopefully resolved this issue. In order to correctly prioritize issues in our upcoming release, we are closing this bug. If you continue to experience your issue on the latest stable version of Android Studio, please submit a new bug report. We apologize for any inconvenience this may cause you.
Description
With the introduction of .aar packages and its support by mavenCentral/jCenter repositories, the use of 3rd party libraries can easily and silently lead to the inclusion of .so files inside apps.
However, Android now supports 7 different ABIs and library developers are rarely providing native libraries for all of them.
Hence it's really easy to develop an application and include libraries, let's say libA and liB, which are supporting different platforms:
libA.aar with jni/(armeabi-v7a,x86,arm64-v8a,x86_64) folders with .so files
libB.aar with only jni/(armeabi-v7a,x86) folders with .so files
Testing such application would go perfectly fine on armv7 and x86 devices/emulators which are the one usually tested, but the app wouldn't work on x86_64, arm64-v8a and other environments that are less common right now.
To limit this issue, a lint warning could be added.
This warning would be triggered if the final app is going to have lib/(armeabi,armeabi-v7a,arm64-v8a,x86,x86_64,mips,mips64) folders with different set of libraries inside, to ensure the developer knows what he's doing.