Manage Dependency Conflicts with Third‑Party Plugins (HERE SDK for Android)

If you encounter a MISSING_LIBRARIES error while using the HERE SDK for Android, it is usually caused by either an incorrect folder structure for native libraries or a conflict with another dependency.

### Fix 1: Correct the native library folder

Ensure that your .so files are placed in the correct directory:

 /app/src/main/jniLibs/armeabi-v7a/ 

---

### Fix 2: Resolve dependency conflict using ABI configuration

If another dependency includes native libraries, update your build.gradle file as follows:

 android { (...) splits { abi { enable true reset() include 'x86_64', 'arm64-v8a' // Choose what you need. universalApk false } } (...)} 

---

Symptoms
--------

You may see this issue when:

The app crashes at runtime with:

 MISSING_LIBRARIES error 
The app builds successfully but fails to load native libraries
Logs indicate missing or conflicting .so files

---

Cause
-----

This issue typically occurs due to one of the following:

1. Incorrect folder structure

Native .so files are not placed under the expected jniLibs/armeabi-v7a directory
2. Conflicting dependencies

Another SDK or plugin includes native libraries that conflict with HERE SDK libraries

---

Additional Notes
----------------

Ensure that all native libraries are placed inside the correct jniLibs directory structure
Avoid including multiple SDKs that bundle overlapping native libraries
Verify ABI compatibility for your target devices

---

Additional Reference
--------------------

For more details on ABI configuration and optimisation, refer to:
https://docs.here.com/here-sdk/docs/key-concepts#use-abi-splits-for-android-to-remove-unused-abis