0

I have two apps A and B. App A uses DexClassLoader to load a custom view class from app B. This works fine.

However if the custom view in app B loads private native libraries bundled with apk B via java.lang.System.loadLibrary and dalvik.system.PathClassLoader. Then I get

 java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.example.app-b-xxx==/base.apk"],nativeLibraryDirectories=[/system/lib, /vendor/lib]]] couldn't find "my_native_lib.so"

If I start app B by itself, it is able to load the private native libraries just fine.

Is this supported? I know that DexClassLoader only loads classes, but can those loaded classes then call into their own bundled native libs?

tir38
  • 9,810
  • 10
  • 64
  • 107

2 Answers2

0

You really shouldn't be loading classes directly like that at all, you'll probably get in trouble with Google for it. I believe it's against the TOS of the Play Store. It's also just not safe- if some other app with the same name is installed pretending to be you, you just allowed their code to run as your user, a massive security issue.

But let's ignore that. Here's why it isn't working- your app doesn't have that library. When you load via loadLibrary, it's looking in a particular path that's local to your app for the .so file. "your app" in this context is the app that's running, not the app that the code comes from. So it's looking in the wrong place. It might work if you include the .so file in both apps. But you'd obviously need to know that implementation detail to make it work, you couldn't use this to load any random class' libraries.

Gabe Sechan
  • 90,003
  • 9
  • 87
  • 127
  • I control both of these apps. This is running on a device w/out Play Store / Play Services (just plain old AOSP). There are unfortunately other reasons why I can't bundle the native code in *both* apps. – tir38 Mar 21 '22 at 22:52
  • Then you're kind of stuck. If you own the only devices it will run on, you could adb push them to a system libary directory, that could work. But you can't load a library from another app's directory, you don't have the right file permissions. – Gabe Sechan Mar 22 '22 at 00:17
  • That's not a bad idea, since it'll also look in `nativeLibraryDirectories=[/system/lib, /vendor/lib]]` Thanks for your help. – tir38 Mar 25 '22 at 20:27
0

If you're willing to use a bit of reflection, the DexClassLoader contains a private field called pathList that then holds a method called addNativePath(Collection<String>).

To get App B's native library directory, you can load it through the package manager.

// assumes currently in an activity

val nativeLibraryPath = packageManager.getPackageInfo("com.package.name", 0).applicationInfo.nativeLibraryDir

val clClass = classLoader.javaClass
val plField = clClass.superclass.getDeclaredField("pathList")
plField.isAccessible = true

val plInst = plField.get(classLoader)
val plClass = plClass.javaClass

val anpMethod = plClass.getDeclaredMethod("addNativePath", Collection::class.java)
anpMethod.invoke(
  plInst,
  listOf(nativeLibraryPath)
)

Keep in mind that as this uses hidden API methods, this may stop working in some newer version of Android. (The code I wrote was primarily tested on Android 11)

If you're using System.loadLibrary to load the native library (which doesn't seem to be the case based on the provided error), just using System.load with an absolute path to the native library from App B will work without playing around with the class loader.

Chloe
  • 36
  • 1
  • 4