java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader

Question

Is there someone who had experience with this error?

java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/org.swig.simple-2/base.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]] couldn't find "liborg.swig.simple.example.so"

Error occurs when I load library by this way.

static {
    System.loadLibrary("example");
}

I'm sure 'example' class is exist in the current folder.

I test all 15 answers but my problem not solved. what should do? ```java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.allInOne.gifemaker-1/base.apk"],nativeLibraryDirectories=[/data/app/com.allInOne.gifemaker-1/lib/arm, /data/app/com.allInOne.gifemaker-1/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib, system/vendor/lib, system/vendor/lib/egl, system/lib/hw]]] couldn't find "libavutil.so" at java.lang.Runtime.loadLibrary(Runtime.java:367)``` — Sana Ebadi, Sep 25 '19 at 20:33

King of Masses · Answer 1 · 2019-12-27T03:51:29.437

61

I am currently working on an Android application which streams radio. I use native decoder library which is called aacdecoder. Everything was fine till app gets crash error on some Android devices. It was really annoying. Because app was perfectly plays radio streams almost all devices but Samsung S6 and S6 Edge.

Crash report says that

Fatal Exception: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file “/data/app/com.radyoland.android-1/base.apk”],nativeLibraryDirectories=[/data/app/com.radyoland.android-1/lib/arm64, /vendor/lib64, /system/lib64]]] couldn’t find “libaacdecoder.so”
 at java.lang.Runtime.loadLibrary(Runtime.java:366)
 at java.lang.System.loadLibrary(System.java:988)
 at com.spoledge.aacdecoder.Decoder.loadLibrary(Decoder.java:187)

As you see that crash is saying that it could not load native library. But why? First of all I checked my structure, If native library .so files located correctly.

Seems everything was okay except this crazy error. Then after some research, I find out that some of android devices has 64-bit processors. This devices generates and check arm64 folder to load native library. That was the problem. Because my project does not have arm64 folder. Here is the solution;

defaultConfig {
    ...

    ndk {
        abiFilters "armeabi-v7a", "x86", "armeabi", "mips"
    }

}

You need to add this filters(abiFilters) to your app module’s build.gradle files. So when your device try to run your app, it will check gradle file and understands that it should not generate any folder and use existing native library resources. Boom, almost solved. But still there is one more thing.

android.useDeprecatedNdk=true

Add this line to your gradle.properties to use deprecated Ndk.

Finally my app works on S6 and S6 Edge. I mean it works on every devices which has new 64-bit processors.

Update :

As of Dec/2019 armabi and mips are deprecated. Supported ABIs are [arm64-v8a, armeabi-v7a, x86, x86_64]

So, your code should be like this

defaultConfig {
        ...

        ndk {
            abiFilters "arm64-v8a", "armeabi-v7a", "x86", "x86_64"
        }

    }

edited Dec 27 '19 at 03:51

answered Sep 05 '17 at 09:14

King of Masses

18,405
4
60
77

1

thanks! this was the only solution that worked for me – Leonardo Assunção Jan 02 '18 at 18:13
1

android.useDeprecatedNdk=true this flag is depreciated – Muhammad Noman May 16 '19 at 04:56
2

as of Dec/2019 armabi and mips are deprecated. Supported ABIs are [arm64-v8a, armeabi-v7a, x86, x86_64]. – Aman Dec 26 '19 at 13:18
can someone help me? it doesn't work, my app keeps crashing on Pixel 2... – tomeda Mar 28 '20 at 04:33
@RuberandindaPatience – tomeda Mar 28 '20 at 04:33
@tomeda In my build.gradle file file I remains with `abiFilters "x86", "armeabi"` only. for me to work on my devices. – Ruberandinda Patience Mar 28 '20 at 10:45
@RuberandindaPatience Thanks for reply. But doesn't this means if I build appgradle it won't generate for 64 bits? google playstore requires all – tomeda Mar 30 '20 at 02:50
original answer is [here](https://medium.com/mobiwise-blog/unsatisfiedlinkerror-problem-on-some-android-devices-b77f2f83837d) – Cagdas Sep 23 '20 at 06:04
Only this answer work for me. I added my files into the jniLibs into my app/src/main folder but it didn't work. Adding the `abiFilters` save my day. – user3502626 Jun 09 '21 at 01:10
even using the relevant `abiFilters`, if you run apk on a device that does not have the relevant native libraries compiled for it, then they system cannot find them. For example, `abiFilters "x86"` but running on ARM emulator will crash. – Pnemonic Feb 20 '23 at 14:00

score 55 · Accepted Answer · answered Nov 28 '14 at 11:04

55

Please note that there's a naming convention. Your lib needs to be called libexample.so .

LoadLibrary("example") will look for libexample.so.

The .so library needs to be inside the apk under the lib folder (since you are developing for Android, it needs to be under the lib/armeabi and lib/armeabi-v7a folders - why both folders ? some versions of Android look under lib/armeabi and some look under lib/armeabi-v7a ... se what works for you ).

Other things to look for :

make sure you compile for the correct architecture (if you compile for armeabi v5 it won't work on armeabiv7 or armeabiv7s ).
make sure your exported prototypes are used in the correct class (check the hello jni example. Your exposed functions need to look something like Java_mypackagename_myjavabridgeclass_myfunction).

For example the function Java_com_example_sample_hello will translate in the java class com.example.sample , function hello.

answered Nov 28 '14 at 11:04

MichaelCMS

4,703
2
23
29

I downloaded this example http://www.swig.org/Doc2.0/Android.html#Android_examples_intro My CBU/ABI is armeabi-v7a is there any solution ? – developergg Nov 28 '14 at 11:38
1

If you are new to jni, use the google example : https://code.google.com/p/awesomeguy/wiki/JNITutorial . I personally don't like swig, I avoid using it. Swig will add an extra level of compexity to your code, and since you don't fully grasp the jni concept it's better to avoid it at first (swig generates things for you ... you need to know what these things are and how they are used before you can fully benefit from what swig is offering ;) ) – MichaelCMS Nov 28 '14 at 11:57
I have not any choice. Because my client provides me a C++ function which I have to call from my java code. – developergg Nov 28 '14 at 12:05
1

I was simply giving a hint on where to start to understand jni. I cannot provide blindly a solution for your context :). – MichaelCMS Nov 28 '14 at 12:49
saved me, struggled for a day for that things, i only had for armeabiv7 and not for armeabi-v7a – Vikas Pandey Jul 07 '17 at 12:50
I have the same issue like a @developergg but only on Sony phones with Android 7 and 8. I have the following abifilters: "armeabi-v7a", "arm64-v8a". On another devices works fine. Is there any ideas? – ilyamuromets May 04 '18 at 14:56

score 39 · Answer 3 · answered Jul 05 '16 at 20:33

39

This helped me. Sharing it for someone who might come up with same issue.

android {
    ....
    defaultConfig {
        ....
        ndk {
            abiFilters "armeabi", "armeabi-v7a", "x86", "mips"
        }
    }
}

answered Jul 05 '16 at 20:33

Alex

1,052
1
11
22

7

This doesn't explain why it helped you. I am facing the said issue, and already have **abiFilters** setup. – IgorGanapolsky Sep 16 '16 at 14:05
Thanks, I only had 'armeabi' and was wondering why libc++_shared.so in my armeabi-v7a library cannot be found!! Wow, without your pointer Idk how I could see it myself. – TastyCatFood Mar 25 '17 at 12:16
This helped me, I still don't know why it works. but thank you! – Marty Miller Aug 29 '17 at 01:40
Thanks Man Save My Day. – P A Gosai Dec 17 '19 at 11:02

score 13 · Answer 4 · answered May 04 '16 at 21:39

What worked for me was to place the jniLibs folder under the "main" folder, just besides the "java" and "res" folders, for example project -> app -> src -> main -> jniLibs

I had all the libraries with the correct names and each one placed on their respective architecture subfolder, but I still had the same exception; even tried a lot of other SO answers like the accepted answer here, compiling a JAR with the .so libs, other placing of the jniLibs folder, etc.

For this project, I had to use Gradle 2.2 and Android Plugin 1.1.0 on Android Studio 1.5.1

Sanket Sangani · Answer 5 · 2018-02-16T14:18:15.120

9

-if gradle.properties not available then first add that file and add android.useDeprecatedNdk=true

-use this code in build.gradle

defaultConfig {
    applicationId 'com.example.application'
    minSdkVersion 16
    targetSdkVersion 21
    versionCode 11
    versionName "1.1"
    ndk {
        abiFilters "armeabi"
    }
}

`

edited Feb 16 '18 at 14:18

answered Feb 14 '18 at 12:19

Sanket Sangani

253
3
10

Smiles · Answer 6 · 2017-07-07T04:26:50.857

8

I use Android Studio 3.0 and encounter this problem. And I'm sure app's build.gradle is OK.

Go to Run -> Edit Configurations -> Profiling, and disable "Enable advanced profiling".

This works for me. Reference answer

edited Jul 07 '17 at 04:26

answered Jun 26 '17 at 07:07

Smiles

481
1
6
15

but why though?. – miracle-doh May 25 '18 at 07:28
Thanks a ton for this. I had enabled advanced profilling for debugging network traffic but the next day I got this error and was left puzzled about why. – Warpzit Jun 15 '18 at 07:44

score 8 · Answer 7 · answered Nov 02 '17 at 08:30

8

This is worked for me

If your having .so file in armeabi then mention inside ndk that folder alone.

defaultConfig {
        applicationId "com.xxx.yyy"
        minSdkVersion 17
        targetSdkVersion 26
        versionCode 1
        versionName "1.0"
        renderscriptTargetApi 26
        renderscriptSupportModeEnabled true
        ndk {
            abiFilters "armeabi"
        }
    }

and then use this

android.useDeprecatedNdk=true;

in gradle.properties file

answered Nov 02 '17 at 08:30

KCN

472
6
19

Could not find method abiFilters() for arguments [armeabi] on project – Roman Soviak Aug 03 '18 at 10:21
Dont include comma after This is worked for me If your having .so file in armeabi then mention inside ndk that folder alone. defaultConfig { applicationId "com.xxx.yyy" minSdkVersion 17 targetSdkVersion 26 versionCode 1 versionName "1.0" renderscriptTargetApi 26 renderscriptSupportModeEnabled true ndk { abiFilters "armeabi" } } and then use this android.useDeprecatedNdk=true; just use android.useDeprecatedNdk=true without comma – Emmanuel Njorodongo Jan 19 '21 at 07:46

score 7 · Answer 8 · answered Apr 05 '18 at 07:38

7

What helped me was to register the source directory for jni files in the build.gradle file. Add this to your gradle file:

android {
    sourceSets {
        main {
            jniLibs.srcDir '[YOUR_JNI_DIR]' // i.e. 'libs'
        }
    }
}

answered Apr 05 '18 at 07:38

Boris Gitlin

146
2
4

this is work for me ! In my case I point to libs dir which contains *.so file – linjiejun Sep 28 '22 at 10:23

score 5 · Answer 9 · answered Mar 25 '16 at 03:20

5

Some old gradle tools cannot copy .so files into build folder by somehow, manually copying these files into build folder as below can solve the problem:

build/intermediates/rs/{build config}/{support architecture}/

build config: beta/production/sit/uat

support architecture: armeabi/armeabi-v7a/mips/x86

answered Mar 25 '16 at 03:20

thanhbinh84

17,876
6
62
69

1

Strange, maybe it's an Android Studio bug? Same thing with **jniLibs** folder. – IgorGanapolsky Sep 15 '16 at 20:01

score 5 · Answer 10 · answered Feb 08 '18 at 18:17

If you are using Android studio, just edit the gradle.properties in the root folder and add android.useDeprecatedNdk=true. Then edit the build.gradle file in your app's folder, set abiFilters as below:

android {
....
defaultConfig {
    ....
    ndk {
        abiFilters "armeabi", "armeabi-v7a", "x86", "mips"
    }
}
}

Sergei Belozerov · Answer 11 · 2018-02-22T10:29:00.907

2

If you use module with c++ code and have the same issue you could try

Build -> Refresh Linked C++ Projects

Also, you should open some file from this module and do

Build -> Make module "YourNativeLibModuleName"

edited Feb 22 '18 at 10:29

answered Jan 23 '18 at 12:28

Sergei Belozerov

341
4
12

score 2 · Answer 12 · answered Feb 22 '20 at 16:46

Ensure you have included the different abiFilters, this enables Gradle know what ABI libraries to package into your apk.

defaultConfig {
 ndk { 
       abiFilters "armeabi-v7a", "x86", "armeabi", "mips" 
     } 
  }

If you storing your jni libs in a different directory, or also using externally linked jni libs, Include them on the different source sets of the app.

sourceSets { 
  main { 
    jni.srcDirs = ['src/main/jniLibs'] 
    jniLibs.srcDir 'src/main/jniLibs' 
    } 
}

score 1 · Answer 13 · answered May 08 '18 at 07:54

1

Yet another crash cause and possible solution is described in this article: https://medium.com/keepsafe-engineering/the-perils-of-loading-native-libraries-on-android-befa49dce2db

Briefly:
in build.gradle

dependencies {
    implementation 'com.getkeepsafe.relinker:relinker:1.2.3'
}

in code

static {
    try {
        System.loadLibrary("<your_libs_name>");
    } catch (UnsatisfiedLinkError e) {
        ReLinker.loadLibrary(context, "<your_libs_name>");
    }
}

answered May 08 '18 at 07:54

ilyamuromets

403
1
7
18

How are you planning to pass the context in a static block? – Cyph3rCod3r Feb 10 '20 at 05:17
@Dr.aNdRO I refactored static block to static method. And now I'm calling it in the CustomApplication class. – ilyamuromets Feb 10 '20 at 08:06
or you can create a helper with context alive :D – Cyph3rCod3r Feb 12 '20 at 12:09

score 1 · Answer 14 · answered Nov 08 '21 at 12:14

I have resolved my issue by adding these lines.

defaultConfig {
 ndk { 
       abiFilters "armeabi-v7a", "x86", "armeabi", "mips" 
     } 
  }
sourceSets { 
  main { 
    jni.srcDirs = ['src/main/jniLibs'] 
    jniLibs.srcDir 'src/main/jniLibs' 
    } 
}

score 0 · Answer 15 · answered Mar 24 '16 at 14:20

For me the problem was in NDK_ROOT not being set.

Check your console if:

NDK_ROOT = None [!] NDK_ROOT not defined. Please define NDK_ROOT in your environment or in local.properties

Check if you have set:

NDK_ROOT and SDK_ROOT in C/C++->Build->Environment
Android->NDK
Android->SDK

score 0 · Answer 16 · answered Jul 31 '17 at 09:24

This could be device related issue.
I was getting this error in MI devices only, code was working with all other devices.

This might help:

 defaultConfig{
      ...    
      externalNativeBuild {
                    cmake {
                        cppFlags "-frtti -fexceptions"
                    }
                }
    }

score 0 · Answer 17 · answered Oct 31 '19 at 11:20

Simple Solution with Pics

Step1: Add following code in build.gradle file under defaultConfig

     ndk {
            abiFilters "armeabi-v7a", "x86", "armeabi", "mips"
        }
Example:[![enter image description here][1]][1]


Steo 2: Add following code in gradle.properties file

android.useDeprecatedNdk=true

Example: [![enter image description here][2]][2]

Step 3: Sync Gradle and Run the Project.

@Ambilpur


  [1]: https://i.stack.imgur.com/IPw4y.png
  [2]: https://i.stack.imgur.com/ByMoh.png

score 0 · Answer 18 · answered Nov 11 '20 at 08:24

In my case After running the ndk-build in the jni folder the shared library was created under the libs folder but the path specified in build.gradle

sourceSets.main {
        jni.srcDirs = []
        jniLibs.srcDir 'src/main/jniLibs'
    }

so I need to move the created shared library to jnilibs folder and it worked!

score 0 · Answer 19 · answered Jun 28 '22 at 18:00

0

Copy your "example.so" file inside /libs/(armeabi|armeabi-v7a|x86|...) . When using Android Studio, it's /app/src/main/jniLibs/(armeabi|armeabi-v7a|x86|...)

answered Jun 28 '22 at 18:00

Kangudie Muanza - Killmonger

1,249
10
12

score 0 · Answer 20 · answered Oct 24 '22 at 15:08

This is how I fixed this particular issue

include below code in app level build.gradle insideandroid { }

externalNativeBuild {
        cmake {
            path "/CMakeLists.txt"
           
        }
    }

Ensure CMakeLists.txt exists in correct location

Ensure CMake and NDK are installed. Follow steps mentioned here to install the same

https://developer.android.com/studio/projects/install-ndk

The native files were inside jni folder, which was under Main folder as shown

I neither used

ndk {
            abiFilters "arm64-v8a", "armeabi-v7a", "x86", "x86_64"
        }

nor included

android.useDeprecatedNdk=true

in gradle.properties file

If everything done correctly in 'build' tab we can see

Task :NightSkyApps:buildCMakeDebug[x86]

Task :NightSkyApps:configureCMakeDebug[x86_64]

Task :NightSkyApps:buildCMakeDebug[x86_64]

If anything goes wrong then above tasks fails which can be seen in 'build' tab.

I faced issue on Android Studio emulator Pixel 4: API 31. Android Studio version

Android Studio Dolphin | 2021.3.1
Build #AI-213.7172.25.2113.9014738, built on September 1, 2022

Build gradle

classpath 'com.android.tools.build:gradle:7.2.2'

score 0 · Answer 21 · answered Jun 02 '23 at 13:12

0

If you have old device try to rename "armeabi" folder to "armeabi-v7a". It fixed this issue for me because i dont realized, that i had device with 32-bit ARM-based CPU.

https://developer.android.com/ndk/guides/abis#v7a

answered Jun 02 '23 at 13:12

Michael Janošík

11
3

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jun 02 '23 at 16:59

java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader

21 Answers21

Linked