Hello. Some time ago we started receiving very interesting crash reports in our crashlytics about scichart init. We can’t reproduce it by ourselves, but there are a lot of samples from our users with different devices and with different Android OS.
Fatal Exception: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.**.**-WqNyhtp24SkSTYz13S2c3w==/base.apk"],nativeLibraryDirectories=[/data/app/com.**.**-WqNyhtp24SkSTYz13S2c3w==/lib/arm64, /system/lib64]]] couldn't find "libcore.so"
at java.lang.Runtime.loadLibrary0(Runtime.java:1067)
at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
at java.lang.System.loadLibrary(System.java:1667)
at com.scichart.core.utility.NativeLibraryHelper.tryLoadLibrary(SourceFile:2)
at com.scichart.core.utility.NativeLibraryHelper.tryLoadCoreLibrary(:2)
at com.scichart.core.licensing.Credentials.<clinit>(SourceFile:1)
at com.scichart.core.licensing.Credentials.setRuntimeLicenseKey(SourceFile:1)
at com.scichart.charting.visuals.SciChartSurface.setRuntimeLicenseKey()
At our last build we added
abi {
enableSplit = false
}
This action reduced the number of crashes, but it still happens:
Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: couldn't map "/mnt/asec/com.**.**-2/base.apk!/lib/armeabi-v7a/libcore.so" segment 1: Permission denied
at java.lang.Runtime.loadLibrary0(Runtime.java:989)
at java.lang.System.loadLibrary(System.java:1567)
at com.scichart.core.utility.NativeLibraryHelper.tryLoadLibrary(SourceFile:2)
at com.scichart.core.utility.NativeLibraryHelper.tryLoadCoreLibrary(SourceFile)
at com.scichart.core.licensing.Credentials.<clinit>(SourceFile:1)
at com.scichart.core.licensing.Credentials.setRuntimeLicenseKey(SourceFile:1)
at com.scichart.charting.visuals.SciChartSurface.setRuntimeLicenseKey(SourceFile)
Have there been similar problems?
- Alexander Ostrovsky asked 1 year ago
- last edited 1 year ago
- You must login to post comments
Hi Alexander
I haven’t heard of any similar reports I’m afraid.
Do you know anything about what patterns of devices or OS versions might be present? Also what proportion of users is this affecting?
This article I found talks about the perils of loading native libraries on Android. That’s what’s happening here, the stack trace is trying to load SciChart’s core C++ library (used for licensing & rendering).
There’s some possible ways to debug this & come to a solution in that article and possibly something we can do by using Relinker to load a library, although would require some way to reproduce this so we can test it.
Best regards
Andrew
- Andrew Burnett-Thompson answered 1 year ago
- last edited 1 year ago
- You must login to post comments
Hi Andrew.
Thank you for your quick response.
There are no specific devices or operating systems, And, as you can see, we didn’t support devices with very old Android versions.
I have no idea what We can do in this case, but if You have the same other ideas, or if You make some changes – just notice me.
- Alexander Ostrovsky answered 1 year ago
- last edited 1 year ago
- You must login to post comments
I’ve seen similar issues with loading libcore.so for some users.
According to Crashlytics, in my case the issue is limited to ROOTED devices.
Maybe someone smarter than me has a clue?
Thank you.
- C Bolton answered 1 year ago
- You must login to post comments
Please login first to submit.