You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2022. It is now read-only.
03-09 21:49:57.368: E/AndroidRuntime(27702): java.lang.UnsatisfiedLinkError: Couldn't load lept from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.datumdroid.android.ocr.simple-2.apk"],nativeLibraryDirectories=[/data/app-lib/com.datumdroid.android.ocr.simple-2, /vendor/lib, /system/lib]]]: findLibrary returned null
This happens here:
03-09 21:49:57.368: E/AndroidRuntime(27702): at com.datumdroid.android.ocr.simple.SimpleAndroidOCRActivity.onPhotoTaken(SimpleAndroidOCRActivity.java:211)
Which is this code:
TessBaseAPI baseApi = new TessBaseAPI();
From previous issues, they have said to make sure the build target is the same in the library as the project, but it is, as seen in these screenshots:
The text was updated successfully, but these errors were encountered:
I can see there is no lib folder (which contain .so files) in your tess-two library. You have to build tess-two with ndk-build before using it. Check this link to setup tess-two and you should read android ndk document first.
For me it kept giving this error even though I had the "libs" folder after building it with ndk-build. I don't know what was going on but I fixed it by renaming the "libs" folder to "lib", packing it as zip and changing the suffix from .zip to .jar. After that I opened my project's properties in Eclipse and added the external jar into Libraries in Java Build Path.
Works, but I have a feeling there would be a better way to do it. There shouldn't be need for this.
I am getting this error:
This happens here:
Which is this code:
From previous issues, they have said to make sure the build target is the same in the library as the project, but it is, as seen in these screenshots:
The text was updated successfully, but these errors were encountered: