Crash upon joining a meeting

Upgrading SDKs
1

Hello,
I am seeing the following crash, after joining meetings, after updating to the latest version of the zoom SDK:

dlopen failed: cannot locate symbol "__emutls_get_address" referenced by "/data/app/~~jt9E1aWsCpnbFMxFnLsuVg==/com.bicyclehealth.patient.app-16_zhBEHvMJUmMPCBl-cHQ==/lib/arm64/libannotate.so"...

It appears I am getting a conflict between two libraries I am using, one being the Zoom SDK (I see this if I remove the pickFirst from packaging options):

2 files found with path 'lib/arm64-v8a/libc++_shared.so' from inputs:
 - /Users/chris/.gradle/caches/transforms-3/05c48075d903ffbc908c04da44693029/transformed/jetified-react-native-0.67.3/jni/arm64-v8a/libc++_shared.so
 - /Users/chris/.gradle/caches/transforms-3/26d25477aaab16d2fc6c550edf665205/transformed/jetified-mobilertc-5.13.1.11014/jni/arm64-v8a/libc++_shared.so

    packagingOptions {
        pickFirst 'lib/arm64-v8a/libc++_shared.so'
        pickFirst 'lib/x86/libc++_shared.so'
        pickFirst 'lib/x86_64/libc++_shared.so'
        pickFirst 'lib/armeabi-v7a/libc++_shared.so'
        pickFirst 'lib/x86_64/libjsc.so'
        pickFirst 'lib/arm64-v8a/libjsc.so'
    }

Is there a way to ensure the correct version of the .so file is being picked? Intermittently builds seem to happen where I can join calls fine, but I don’t want to have to build several times and have to check each time if zoom calls are working.

1 Like
2

Hi Christopher,
Hope so you’re doing good this week, identify the library that is conflicting with the Zoom SDK and remove it from your project’s dependencies. You can do this by modifying your project’s build.gradle file or by updating the library version to a compatible one. In your packagingOptions configuration, make sure to specify the correct version of the libc++_shared.so file for the desired architecture. You can use the pickFirst directive to prioritize the correct version, ensuring it is selected during the build process. After making the necessary changes, clean your project and perform a full rebuild to ensure that the changes take effect properly. This will help ensure that the correct libraries are included and conflicts are resolved. Hope so this will work for you!
Regards,
Bryce June

3

I had the same error, using packagingOptions it even solved it, but only for some devices, on the xiaomi mi 11t ultra for example it didn’t work yet.