iOS linking issues

Mon, 01 Jan 0001 00:00:00 +0000

**⚠️ Legacy (v1.x)** — You are viewing the old documentation. [View current v2.0 docs](/)

If your iOS build fails during the link step, it’s usually one of these:

1) Relative paths inside published artifacts#

If you see errors like “search path not found” or “library not found”, check whether any .def / linkerOpts are using relative paths that don’t exist in the consumer project.

Fix: ensure published artifacts don’t encode build-machine-relative paths. Prefer packaging the needed native libs inside the artifact (or use absolute paths generated at build time).

Android native loading issues

Mon, 01 Jan 0001 00:00:00 +0000

**⚠️ Legacy (v1.x)** — You are viewing the old documentation. [View current v2.0 docs](/)

If you get UnsatisfiedLinkError on Android, it usually means:

1) The native library is missing for the ABI#

Make sure the correct .so is packaged for your device ABI (arm64-v8a, etc.).

2) Loading happens too early / in the wrong classloader#

Llamatik’s Android implementation loads its JNI library. If you have a custom setup, ensure the load happens in a place that runs once and before any native calls.

Troubleshooting on Llamatik Documentation

iOS linking issues

1) Relative paths inside published artifacts#

Android native loading issues

1) The native library is missing for the ABI#

2) Loading happens too early / in the wrong classloader#