Closed libreliodev closed 9 years ago
UnsatisfiedLinkError is usually thrown when an app cannot call a native library. In this case the MuPDF library cannot be called.
It looks like the device is an ARM device so the native library should be there.
@intrications So, does this mean that some specific devices cannot use the app, because they can't use MuPDF?
@libreliodev I wouldn't think so. Any device should be able to call native libraries. The only reason I mentioned ARM is that some devices may be MIPS or x86. But x86, if not MIPS as well, emulates ARM in order to run ARM libraries: http://stackoverflow.com/a/13005569/84021
So I expect there's some other reason for the error.
@libreliodev Is there any evidence that this wasn't a one-off crash?
I think we should close this issue for now and improve crash reporting. #282
I had the same crash using my emulator, It has API 19 and x86 processor The full error report in the logcat is following
E/AndroidRuntime( 2464): FATAL EXCEPTION: main
E/AndroidRuntime( 2464): Process: com.artifex.mupdfdemo, PID: 2464
E/AndroidRuntime( 2464): java.lang.UnsatisfiedLinkError: Couldn't load mupdf_java32 from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.artifex.mupdfdemo-2.apk"],nativeLibraryDirectories=[/data/app-lib/com.artifex.mupdfdemo-2, /system/lib]]]: findLibrary returned null
E/AndroidRuntime( 2464): at java.lang.Runtime.loadLibrary(Runtime.java:358)
E/AndroidRuntime( 2464): at java.lang.System.loadLibrary(System.java:526)
E/AndroidRuntime( 2464): at com.artifex.mupdfdemo.MuPDFCore.
@intrications This was reported 3 mn after #254 by same user