Buildtools should not affect this. Can you check if your library is packaged into the .apk?
Do you have an example project that reproduces this? Could you file a bug at b.android.com? Thanks On Thursday, September 22, 2016 at 12:33:31 AM UTC-7, Guy Tavor wrote: > > Just checked. > Also happends with 24.0.2 > > Has the place where to put .so files changed? > > > On Wednesday, September 21, 2016 at 1:13:40 PM UTC+3, Makoto Yamazaki > wrote: >> >> How about build-tools 24.0.2? >> >> On Wed, Sep 21, 2016 at 6:53 PM, Guy Tavor <g...@scoompa.com> wrote: >> >>> Further testing narrowed it down to bulid tools 23.0.3: >>> >>> With 23.0.3 we get the UnsatisfiedLinkError, with 23.0.2 everything >>> looks fine like before. >>> >>> Ideas? >>> >>> >>> On Wednesday, September 21, 2016 at 12:01:39 PM UTC+3, Guy Tavor wrote: >>>> >>>> Hello, >>>> >>>> We have a project that includes prebuilt .so files in the src/jniLibs >>>> dir. >>>> >>>> After upgrading to Android Studio 2.2 - Android plugin 2.2.0, build >>>> tools 23.0.3, Gradle 3.1, when running the app, the library is not loaded, >>>> and we get an UnsatisfiedLinkError. >>>> >>>> Was anything changed? could not find relevant information in the >>>> documentation. >>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "adt-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to adt-dev+u...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> YAMAZAKI Makoto >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
