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)
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.
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)) ?
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’m doing some testing now with Web SDK v.1.8.1 and below is my test procedure.
User A joins as host
User B joins as host (will become co-host?)
User C joins as guest
User A left the meeting
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.
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.