App Crashes when starting a meeting in Android devices with latest SDK 5.11.10.8019

Description
Android App crashes while starting a meeting after integration new meeting SDK 5.11.10.8019

Please see the crash logs,
untime.cc:677] JNI DETECTED ERROR IN APPLICATION: JNI CallIntMethodV called with pending exception java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol “__emutls_get_address” referenced by “/data/app/~~buwU9WBkJ4yeXiTHAJnB1g==/-ieQkgCI7v-j1K2mg9FLI-g==/lib/arm64/libannotate.so”…
runtime.cc:677] at void java.lang.Runtime.loadLibrary0(java.lang.ClassLoader, java.lang.Class, java.lang.String) (Runtime.java:1077)
runtime.cc:677] at void java.lang.Runtime.loadLibrary0(java.lang.Class, java.lang.String) (Runtime.java:998)
runtime.cc:677] at void java.lang.System.loadLibrary(java.lang.String) (System.java:1656)
runtime.cc:677] at void com.zipow.videobox.mainboard.module.ZmSdkMainBoard.loadSDKConfAppNativeModules() (ZmSdkMainBoard.java:8)
runtime.cc:677] at void com.zipow.videobox.mainboard.module.ZmSdkMainBoard.createConfAppForSdk(java.lang.String) (ZmSdkMainBoard.java:8)
runtime.cc:677] at void com.zipow.videobox.VideoBoxApplication.initConfAppForSDK(java.lang.String) (VideoBoxApplication.java:23)
runtime.cc:677] at int com.zipow.videobox.VideoBoxApplication.startConfServiceForSDK(android.os.Bundle) (VideoBoxApplication.java:8)
runtime.cc:677] at int com.zipow.videobox.ptapp.ConfProcessMgr.createConfProcess(java.lang.String) (ConfProcessMgr.java:11)
runtime.cc:677] at void com.zipow.videobox.mainboard.Mainboard.notifyUrlActionImpl(java.lang.String) (Mainboard.java:-2)
runtime.cc:677] at void com.zipow.videobox.mainboard.Mainboard.notifyUrlAction(java.lang.String) (Mainboard.java:5)
runtime.cc:677] at void us.zoom.proguard.gu.a(android.content.Context, android.net.Uri) (MeetingServiceImpl.java:11)
runtime.cc:677] at int us.zoom.proguard.gu.startMeetingWithParams(android.content.Context, us.zoom.sdk.StartMeetingParams, us.zoom.sdk.MeetingOptions) (MeetingServiceImpl.java:157)
runtime.cc:677] at void com.ge.remotesharing.RemoteSharingUtils$2.run() (RemoteSharingUtils.java:134)
runtime.cc:677] at void android.os.Handler.handleCallback(android.os.Message) (Handler.java:938)
runtime.cc:677] at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:99)
runtime.cc:677] at boolean android.os.Looper.loopOnce(android.os.Looper, long, int) (Looper.java:233)
runtime.cc:677] at void android.os.Looper.loop() (Looper.java:344)
runtime.cc:677] at void android.app.ActivityThread.main(java.lang.String) (ActivityThread.java:8204)
runtime.cc:677] at java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object) (Method.java:-2)
runtime.cc:677] at void com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run() (RuntimeInit.java:589)
runtime.cc:677] at void com.android.internal.os.ZygoteInit.main(java.lang.String) (ZygoteInit.java:1071)
runtime.cc:677]
runtime.cc:677] in call to CallIntMethodV
runtime.cc:677] from void com.zipow.videobox.mainboard.Mainboard.notifyUrlActionImpl(java.lang.String)

@rssuresh192 ,

Thank you for bringing this to our attention. Can you share if are you seeing this behavior when testing with the sample or only with the integrated application?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.