Alex Konradi 1359b67486 Cache classes during initial Java library load ...

Use the class loader from the main thread to cache java.lang.Class
instances for some libsignal classes.

This enables constructing instances of libsignal classes on threads
where the classes aren't accessible via the default class loader. This
can occur on Android, where threads spawned via the native API only get
access to the system class loader, not the application loader that has
access to the application's class files. Since Tokio worker threads are
spawned via the native API, and the completion process for async tasks
converts results to Java objects, application class instances can't be
used there unless they are preloaded.

Since classes used in client code are only included in the client .jar
file, failure to load classes is a normal occurrence. If there are ever
separate builds for server and client .so library files, this could be
changed to a fatal error.

2024-02-16 10:38:12 -05:00

..

src

Cache classes during initial Java library load

2024-02-16 10:38:12 -05:00

build.gradle

Java: Add -Xcheck:jni to host testing

2023-11-15 10:17:26 -08:00