Hey @prasanna8,
As it turns out, this is a know issue that we’re working on fixing. Apologies for the trouble—we’ll let you know once we have an update on resolving this! (CS-2192)
Thanks,
Will
Hey @prasanna8,
As it turns out, this is a know issue that we’re working on fixing. Apologies for the trouble—we’ll let you know once we have an update on resolving this! (CS-2192)
Thanks,
Will
HI @will.zoom,
Is there any target date for the release of this fix? This is actually a critical issue on our side.
Regards,
Lara
Hey @lfrancia, @prasanna8,
With version 1.8.0, if the host gets disconnected, use the same host signature (passing in role 1) and they will rejoin the meeting as the Co-Host.
That being said, the currently functionality if the host gets disconnected, one of the participants will be assigned the Host. Once the original Host rejoins, they will be the Co-Host.
Thanks,
Tommy
Hi Tommy,
Thank you for the information. So in situation below, all will be hosts (User B will be main host, User A will be the co-host)?
Regards,
Lara
I want to get this point clear.
So, will they rejoin as a participant if they pass in any other signature than the same one they used to host the meeting(even if the new signature is designed to be host(role = 1)) ?
I indicated why this new behavior introduced recently (not related to web SDK version) is not acceptable here, could you please have a look ?
Hey @prasanna8,
The current functionality is if you pass in role 1, they will become the co-host. If you pass in role 0 they will join as a participant.
Thanks,
Tommy
Hey @lfrancia,
Correct:
Thanks,
Tommy
Hi @tommy,
Thank you for answering my question.
If all will be host, then this will really be a problem for us because it means that our clients (originally joined as guest) will be host while the original host will just become co-host. There are reasons why we set our clients as guests and not host.
I hope Zoom can find a better solution for this.
Regards,
Lara
Hey @lfrancia,
We are currently working on a better solution. I will keep this thread updated on its development.
Thanks,
Tommy
Hi @tommy,
I’m doing some testing now with Web SDK v.1.8.1 and below is my test procedure.
I am expecting that User B will be the host right after doing the procedure above. But, what happened was User C instead became the host. Is this the expected behavior? Because, I thought there is a concept of co-host on Web SDK based on your comments.
Could you please confirm?
Regards,
Lara
Hey @lfrancia,
For step 2. do you have the Co Host feature enabled for the meeting host (Host A)?
Thanks,
Tommy
Hi Tommy,
Thank you for your reply.
I was able to make the co-host work after enabling co-host from our account settings. Thank you.
Lara
You are welcome!
Thanks,
Tommy
Hi @tommy,
We will just wait for the update on the original issue since even as co-host, co-host cannot still promote himself to host so the problem is still there.
Regards,
Lara
Correct. I will keep you updated.
Thanks,
Tommy
Hey @PQAITSupport,
We do not have any updates to share yet, other than we are working on this.
Thanks,
Tommy
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.