So I'm providing binaries as a remote dependency packaged as an aar. The android library has the libMyLibrary.so files in the src/main/jniLibs/<abi>/ directory, so when built and deployed they're in the aar's jni dir. The only other thing the library has is a manifest file containing nothing but the package name package.name.A
importing package.name.A as dependency on a different project, different.package.B, results in everything being packaged properly on the build and the shared libs are contained in the debug/release apk's lib/<abi>/libMyLibrary.so. They're not being extracted to the application's native directory upon install though.
The actual installed apk shows that the .so files are there in the apk ZipFile(context.applicationInfo.sourceDir).getEntry("lib/${Build.SUPPORTED_ABIS[0]}/libMyLibrary.so") works and I can extract it that way (just not to the application's nativeDir, security exception). And System.mapLibraryName("MyLibrary") returns "libMyLibrary.so"...
They were being extracted before I supplied them as a remote dependency, and were contained in the application's src/main/jniLibs/<abi>/ directory. Now, the only way I can get it to extract while supplying them as a remote dependency via an aar is by including in the Manifest android:extractNativeLibs="true".
How can I get things to extract properly w/o needing to declare that in my Manifest?
Is there something I need to declare in the remote library's Manifest so upon merge, Android knows about the shared native lib and it will extract properly? Do I need an Android.mk file?
Guidance/help would be very much appreciated!
Adding to different.package.B's build.gradle android block
compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 }
resolved my issue. The *.so files provided via the aar now extract to the application's native directory.