Absolute paths for native libraries

Information on how to store native libraries out of the APK.

阅读时间1 分钟

最后更新于 8 个月前

If you plan to split up your Android application to reduce the initial download size, then you are probably looking to use Android App Bundles with Play Feature Delivery or APK Expansion Files (OBB). For more information, see the Android developer documentation on Play Feature Delivery and APK Expansion Files.

When using Play Feature Delivery or APK Expansion Files, you can choose to store some native libraries outside of the APK. To do this, you need to provide absolute paths to those native libraries.

For example, if

libvivox-sdk.so

is stored outside of the APK, specify this by calling a

JNIHelpers.init(...)

function that accepts the

vivoxLibraryPath

parameter:


JNIHelpers.init("/the/absolute/path/to/libvivox-sdk.so", context)

After

vivox-sdk

is loaded, any additional libraries that you specify to load through

JNIHelpers.init(..., String[] libs)

work based on whether they are an absolute path:

If the library string is an absolute path (which typically means that the path starts with / on Android), then
```
System.load(...)
```
is used to load the library from that absolute path.
If the library string is not an absolute path (the path does not start with / on Android), then it is assumed to be a library name without the
```
lib
```
prefix or the
```
.so
```
ending, and is used with
```
System.loadLibrary(...)
```
to load the library.

文档

Development

User Acquisition

Monetization

工业

文档