Closed libreliodev closed 9 years ago
Not really. Try rebuilding the APK and reinstalling.
still the same after rebuilding and reinstallation many times.
@Ageleswari Can you upload the crash report here or on Gist?
12-10 17:28:12.957 8911-12620/com.client.magazine E/ACRA﹕ com.client.magazine fatal error : Couldn't load mupdf from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.client.magazine-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.client.magazine-1, /vendor/lib, /system/lib]]]: findLibrary returned null
java.lang.UnsatisfiedLinkError: Couldn't load mupdf from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.client.magazine-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.client.magazine-1, /vendor/lib, /system/lib]]]: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:358)
at java.lang.System.loadLibrary(System.java:526)
at com.artifex.mupdfdemo.MuPDFCore.
@intrications Do you have other suggestions please?
@Ageleswari Have you tried on a different device or in the emulator?
Have you changed the code at all?
How did you change the package name? In the build.gradle file?
yes i tried in different devices, and all has the same results i did not change the code but i did change the package name. i changed it manually using refactor and rename in the package right clicked menu pop out. (it is the same as my application id)
@Ageleswari
Did you try and compile and run the project before making any changes? If not, then please download a fresh copy of the repo and try.
Please change the package name just by changing the applicationId in the build.gradle file. There is no need to change the package structure.
If you change the package name manually then you will find it very difficult to merge future commits into your code because directories will change name. This could also be the reason why the native MuPDF libraries can't be found.
Hello, sorry took very long to reply, we were busy regarding the app launch. We managed to get the bug fixed. it wasn't because of the package name. It was because we forgot to include few libraries into the project. Thank you.
@Ageleswari Thanks for the feedback.
cc @intrications
I have the same problem so how did you solve it?
put .so libs to jniLibs folder. Example: src/main/jniLibs/*
@intrications : it was reported by @Ageleswari that he could not build the latest version successfully (see crash report sent by him). Any idea why?