i wanted to ask for some help regarding error handling for inline java with b4a. the call which causes the error (actually, it's a crash) concerns declaring an instance of the so called TessBaseAPI in tesseract. the call works fine on all my test devices running os 4.x.x through 5.1, but deploying to my nexus 5 with android 7.1 causes the app to crash with no logging that i can see or know how to extract.
i've trapped for a null value on return from the call (but it doesn't return), and i've tried try/catch
hoping for logging the exception. again, the function never returns. i would try "try throws exception", but i don't know what the exception is, as the crash shows nothing more than "app has stopped. start again?"
i realize tesseract is beyond the scope of the forum, but for the moment at least i would just like
to be able to trap for the crash. if trappable it is. is there some system log output generated automatically by the os and which i could see from b4A? i use BA.Log() after the call returns, but the crash occurs before any return.
the call takes no parameters to fiddle with: TessBaseAPI api = new TessBaseAPI();
and, as i've indicated, the call (indeed the entire test) works fine except on android 7.
the test itself is found at https://www.b4x.com/android/forum/attachments/tesstest-zip.36963/
it was part of a lengthy thread regarding tesseract. while the test is small, the required
ancillary files are not, as you can surmise from the attached snippet:
i realize any one of those additional files could be at the root of the crash, but i'm hoping that if i can
successfully trap for the exception and display it, at least i would have an idea about what i was up against. thanks for any help.
go
i've trapped for a null value on return from the call (but it doesn't return), and i've tried try/catch
hoping for logging the exception. again, the function never returns. i would try "try throws exception", but i don't know what the exception is, as the crash shows nothing more than "app has stopped. start again?"
i realize tesseract is beyond the scope of the forum, but for the moment at least i would just like
to be able to trap for the crash. if trappable it is. is there some system log output generated automatically by the os and which i could see from b4A? i use BA.Log() after the call returns, but the crash occurs before any return.
the call takes no parameters to fiddle with: TessBaseAPI api = new TessBaseAPI();
and, as i've indicated, the call (indeed the entire test) works fine except on android 7.
the test itself is found at https://www.b4x.com/android/forum/attachments/tesstest-zip.36963/
it was part of a lengthy thread regarding tesseract. while the test is small, the required
ancillary files are not, as you can surmise from the attached snippet:
i realize any one of those additional files could be at the root of the crash, but i'm hoping that if i can
successfully trap for the exception and display it, at least i would have an idea about what i was up against. thanks for any help.
go