-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.UnsatisfiedLinkError exception in AndroidUtils_setContext function in MapView #511
Comments
Thanks for reporting this. SDK tries to load native part of the SDK automatically before any
This snippet tries to manually preload the native part and will log the issues. Once you have some additional details from the logs, please share them with us. |
but in the static {
try {
System.loadLibrary("carto_mobile_sdk");
AndroidUtils.attachJVM(MapView.class);
} catch (Throwable t) {
android.util.Log.e("carto_mobile_sdk", "Failed to initialize Carto Mobile Maps SDK, native .so library failed to load?", t);
}
} why we would load it again before |
@AbolfaZlRezaEe Because it fails but the logging of the event is 'local' and you do not see the message. The beforehand loading is just for getting the exception info to a server so we can see the details. |
Ok. We will do this for our next application version and report the issue here(if we see it in the console) |
Well, after a release that We had, We received these stack traces from our crash report. We hope that these are good points enough to catch this exception:
|
@AbolfaZlRezaEe It seems that there are packaging issues, as the native part of the SDK can not be loaded. Can you share your build.gradle file (assuming you are using Android Studio/gradle)? |
@mtehver I think it's good to mention all of our steps for building and using Carto in our application:
or with our
also, we changed the
after We build the application for the Store, We have four libs files of CARTO-SDK We have a guess that the Store sometimes gives the wrong architecture to the users and this is one of the problems that these exceptions are thrown. but we are not sure. so after all these, any idea? |
@AbolfaZlRezaEe Looks good based on the description, all architectures seems to be present in your APK. No idea why the issue occurs on on some devices. One thing you can try - experiment with 'split ABI' settings (described here: https://developer.android.com/studio/build/configure-apk-splits). |
We have an exception in our application that is from CART SDK. unfortunately, we couldn't find any scenario for reproducing this crash on our phones. the stack trace that Google console gives us is this:
this crash happens around 86K for our users! and that isn't good for our application.
also, we found an issue that mentions this exception in 2019 in this link with some details. but there is still no good solution for this issue yet.
we found this issue in these SDKs much more than the others:
also, this crash happens much more in these devices:
We highly need help for this crash and we have no idea that this crash when happening and why it happens. can somebody help us?
The text was updated successfully, but these errors were encountered: