This is not a MyScript issue but rather an integration issue.
Indeed, the libiink.so is using the __sfp_handle_exceptions symbol, which is normally found into the libc++_shared.so. You have to ensure you link against a libc++_shared.so that contains the __sfp_handle_exceptions.
The one we provide in our iink.aar is normally compatible. Using the latter should then work.
Best regards,
Olivier
D
Dipannita Das
said
about 2 years ago
Hi Olivier,
Thank you for you reply. I did not undersand libc++_shared.so. Please elaborate more on "link against a libc++_shared.so that contains the __sfp_handle_exceptions.". Or Provide some link of documentation.
By default, the iink.aar file (it is located into the iink/bin/android/ directory) we provide contains a libc++_shared.so that you can use to build your APK.
I am insisting this is an Android Studio issue, and is not related to MyScript. You can find tutorials or forum posts that explain how to solve such link error.
Best regards,
Olivier
D
Dipannita Das
said
almost 2 years ago
Hi Olivier, The above issue was fixed by applying proguard rules as -keep class com.myscript.* { *; }
But now getting a new error as A/libc: Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x76072e2000 in tid 28233 (elopment.native), pid 28233 (elopment.native)
These errors are occuring at the time of engine creation.
Please help...
D
Dipannita Das
said
almost 2 years ago
Hi Olivier, Please reply..
O
Olivier @MyScript
said
almost 2 years ago
Dear Dipannita,
Indeed, the MyScript libraries shall not be obfuscated.
On your side, apart from the MyScript libraries, are you using other third part libraries? If so, which ones?
Regarding the latest error message, it doesn't help much by itself. Do you have the full log message? We are indeed not even sure it occurs in the MyScript libraries...
Best regards,
Olivier
D
Dipannita Das
said
almost 2 years ago
Hi Olivier, There are many other libraries used in the project...
O
Olivier @MyScript
said
almost 2 years ago
Answer
Dear Dipannita,
we need more information to be able to investigate further.
Without a sample project that allows to reproduce, we will stop working on this topic.
Dipannita Das
Hi.
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__sfp_handle_exceptions" referenced by "/data/app/~~jIOd9WK8On4mUmzASOfovw==/com.careclues.physician.development.native-90Mg6qv2nhPMJhYQty3gaA==/base.apk!/lib/arm64-v8a/libiink.so"...
Dear Dipannita,
we need more information to be able to investigate further.
Without a sample project that allows to reproduce, we will stop working on this topic.
Best regards,
Olivier
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstOlivier @MyScript
Dear Dipannita,
thank you for contacting us.
This is not a MyScript issue but rather an integration issue.
Indeed, the libiink.so is using the __sfp_handle_exceptions symbol, which is normally found into the libc++_shared.so. You have to ensure you link against a libc++_shared.so that contains the __sfp_handle_exceptions.
The one we provide in our iink.aar is normally compatible. Using the latter should then work.
Best regards,
Olivier
Dipannita Das
Hi Olivier,
Thank you for you reply. I did not undersand libc++_shared.so. Please elaborate more on " link against a libc++_shared.so that contains the __sfp_handle_exceptions.".
Or Provide some link of documentation.
Olivier @MyScript
Dear Dipannita,
What I mean is that the libiink.so need the libc++_shared.so ; based on the error message, it is likely it is not included in your APK, while it must be: https://developer.android.com/ndk/guides/cpp-support#cs
By default, the iink.aar file (it is located into the iink/bin/android/ directory) we provide contains a libc++_shared.so that you can use to build your APK.
I am insisting this is an Android Studio issue, and is not related to MyScript. You can find tutorials or forum posts that explain how to solve such link error.
Best regards,
Olivier
Dipannita Das
Hi Olivier,
The above issue was fixed by applying proguard rules as -keep class com.myscript.* { *; } But now getting a new error as A/libc: Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x76072e2000 in tid 28233 (elopment.native), pid 28233 (elopment.native)
These errors are occuring at the time of engine creation. Please help...
Dipannita Das
Hi Olivier,
Please reply..
Olivier @MyScript
Dear Dipannita,
Indeed, the MyScript libraries shall not be obfuscated.
On your side, apart from the MyScript libraries, are you using other third part libraries? If so, which ones?
Regarding the latest error message, it doesn't help much by itself. Do you have the full log message? We are indeed not even sure it occurs in the MyScript libraries...
Best regards,
Olivier
Dipannita Das
Hi Olivier,
There are many other libraries used in the project...
Olivier @MyScript
Dear Dipannita,
we need more information to be able to investigate further.
Without a sample project that allows to reproduce, we will stop working on this topic.
Best regards,
Olivier