Reinitialize ZoomSDK Get Stuck

when I reinitialize ZoomSDK after the first failed due to wrong/expire JWT → ZoomSDKInitializeListener not call

Which Android Meeting SDK version?

To Reproduce(If applicable)

val params = ZoomSDKInitParams().apply {
jwtToken = “…”
domain = “
ZoomSDK.getInstance().initialize(context, this, params)

→ call all step above (with correct JWT) again after the first failed with wrong JWT =>> nothing happened then

Smartphone (please complete the following information):

  • OS: Android 11

Hi @nam, thanks for using our SDK.

I have not been able to reproduce this behavior. At what point are you trying to call initialize again?


Hi @jon.lieblich,
We can reproduce this behavior in zoomSDK sample.

“onCreate()” of InitAuthSDKActivity,
we call InitAuthSDKHelper.getInstance().initSDK(this, this); with wrong JWT

and then “onZoomSDKInitializeResult()” we can call
InitAuthSDKHelper.getInstance().initSDKAgain(this, this) with correct JWT, but nothing happen then.

I also created a Button call “Init Again” in InitAuthSDKActivity , if the first init SDK fail, this button will show, and when we click this button, we call InitAuthSDKHelper.getInstance().initSDKAgain(this, this) → but nothing happen.

You can see some screenshot of the code + video in the drive folder


Hi @nam,

Can you please provide a patch for the sample app so I can see the changes you’ve made to test this? I am still unable to reproduce and I’m not seeing anything wrong with your implementation based on those screenshots.


Hi @jon.lieblich ,

You can run “sample” in the link below to reproduce it.
At firsttime, init sdk will failed due to expired JWT → you can click button “Init Again” (with correct JWT) and see nothing happen then.


Hi @nam,

Thanks for including that. I’m able to reproduce in the modified sample app you have, but I’m not seeing any significant differences in the implementation between what you have and what I was using when unable to reproduce it. We’ll need to investigate this and get back to you.


Hi @jon.lieblich,

Thank you for the investigation

Hi @nam,

No problem! We were also able to identify a fix for this, which should be included in a future release.


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