-
Notifications
You must be signed in to change notification settings - Fork 98
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
Proguard Rules for Azure Communication Library #69
Comments
Hello Habib, Thanks for reaching out and glad to see you trying out the Azure Communication Services Calling SDK. The Calling SDK does not currently support ABIs armeabi-v7a and x86. It looks like you're attempting to use the library on an armeabi-v7a compatible device which will currently not work. Can you try a device/emulator with arm64-v8a or x86 ABI and report back if you're experiencing issues with these ABIs as well? |
Hello Komivi, 2020-10-20 16:12:01.565 31363-31363/? W/System.err: java.lang.ClassNotFoundException: Didn't find class "com.skype.rt.RootToolsHandler" on path: DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/data/app/com.xpertmemos.inpocket-iZ8YADsfac-vZvbU0FYhGA==/base.apk"],nativeLibraryDirectories=[/data/app/com.xpertmemos.inpocket-iZ8YADsfac-vZvbU0FYhGA==/lib/arm64, /data/app/com.xpertmemos.inpocket-iZ8YADsfac-vZvbU0FYhGA==/base.apk!/lib/arm64-v8a, /system/lib64]]
2020-10-20 16:12:01.566 31363-31363/? A/libc: Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 31363 (tmemos.inpocket), pid 31363 (tmemos.inpocket) Thanks |
@shipon-eye NOW you are on the R8 stripped away classes I think :) Here is my proguard file, which seem to work.
|
Right @tompi, that's the issue indeed. I missed portion of @shipon-eye message where he mentioned the issue was specifically with the release build type. These proguard rules will definitely work out. Give it a try and let us know if you're still experiencing isssues, @shipon-eye. |
We have developed an Android video chat application using Azure Communication Service. It is working successfully in Debug mode. But when we make release build, the app crashes when we initialize a call.
We are using 'com.azure.android:azure-communication-calling:1.0.0-beta.2'
Parts of Error Message:
CallClient: Native library $nativeLib failed to load during initialization.
java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.xpertmemos.inpocket-6QXGEXeOIs3FFbOF1JHg5g==/base.apk"],nativeLibraryDirectories=[/data/app/com.xpertmemos.inpocket-6QXGEXeOIs3FFbOF1JHg5g==/lib/arm, /data/app/com.xpertmemos.inpocket-6QXGEXeOIs3FFbOF1JHg5g==/base.apk!/lib/armeabi-v7a, /system/lib, /system/product/lib]]] couldn't find "libskypert.so"
2020-10-18 13:44:16.184 28108-28108/? E/CallClient: Native library $nativeLib failed to load during initialization.
No implementation found for com.azure.communication.calling.status com.azure.communication.calling.NativeLibrary.sam_call_client_create(com.azure.communication.calling.Out) (tried Java_com_azure_communication_calling_NativeLibrary_sam_1call_1client_1create and Java_com_azure_communication_calling_NativeLibrary_sam_1call_1client_1create__Lcom_azure_communication_calling_Out_2)
So far, we think it may be proguard rules issue.
Please help us to resolve this issue.
Regards
Habib
The text was updated successfully, but these errors were encountered: