JNI Crash

We’re facing a crash when starting a meeting with such error:

A/] 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/~~ZA3CVy78y9W6PO8ov2A==/!/lib/arm64-v8a/"...]   at void java.lang.Runtime.loadLibrary0(java.lang.ClassLoader, java.lang.Class, java.lang.String) (]   at void java.lang.Runtime.loadLibrary0(java.lang.Class, java.lang.String) (]   at void java.lang.System.loadLibrary(java.lang.String) (]   at void com.zipow.videobox.mainboard.module.ZmSdkMainBoard.loadSDKConfAppNativeModules() (]   at void com.zipow.videobox.mainboard.module.ZmSdkMainBoard.createConfAppForSdk(java.lang.String) (]   at void com.zipow.videobox.VideoBoxApplication.initConfAppForSDK(java.lang.String) (]   at int com.zipow.videobox.VideoBoxApplication.startConfServiceForSDK(android.os.Bundle) (]   at int com.zipow.videobox.ptapp.ConfProcessMgr.createConfProcess(java.lang.String) (]   at void com.zipow.videobox.mainboard.Mainboard.notifyUrlActionImpl(java.lang.String) (]   at void com.zipow.videobox.mainboard.Mainboard.notifyUrlAction(java.lang.String) (]   at int com.zipow.videobox.confapp.meeting.premeeting.joinscene.ZMJoinByUrl.joinByUrl(android.content.Context, java.lang.String, java.lang.String, boolean) (]   at int com.zipow.videobox.confapp.meeting.premeeting.joinscene.ZMJoinByUrl.joinByUrl(android.content.Context, java.lang.String, boolean) (]   at int com.zipow.videobox.confapp.meeting.premeeting.joinscene.ZMJoinByUrl.startConfrence(android.content.Context) (]   at boolean com.zipow.videobox.JoinByURLActivity.a(, boolean) (

In fact, this issue is a complete follow-up to that issue. I would like to add to the original thread that I have the exact same problem, but the thread is closed without a response.

Which Android Meeting SDK version?

To Reproduce(If applicable)
Just add another dependency that uses lib/arm64-v8a/ to the official sample project

Smartphone (please complete the following information):

  • Device: Galaxy Tab Active4 Pro
  • OS: Android 12
1 Like

Hi @vvysotskyy ,

This issue might cause by the ndk version. Would you please try to upgrade the meeting SDK version to at least 5.12.0 and upgrade the ndk version to at least ndkr23 to see whether the issue has been solved?
Thank you


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