@tommy check this case
This was working fine until mid august. We got reports from our host users that they did not get the host power back after being disconnected and joining again the meeting.
The code on our application did not change and we always pass 1 for our host and 0 for other participants.
Please investigate on it.
Looks like this bug re appeared again and you’re working on according to your reply here:
Same here from one of your colleague
Could you please update all related thread when you have a feedback and fix for this ?
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 have checked with 1.8.0 but it’s not working as we expect still the same issue Participant becomes the host.
This is not how the application use to work before 1.8.0 so please fix it.
Not to mention that :
- your solution would force us to activate the co-host feature from our account settings and we may don’t want it.
- this change do not seems to be related to 1.8.0 as it also break 1.7.10. So this change in on your back-end services and not the SDK itself.
If possible, here is how we would like things to be fixed:
- A participant who temporary get host powers because the host left, should lose its host powers when at least one host participant join / re-join. If some participants join as non host, it is for a reason !
- When the host re-join, if he is the only real host (understand here not a temporary host for technical reasons) he should join as host and not co-host - well unless the co-host option is activated and there is already another real host in the meeting, in such situation i agree to re join as co-host.
Being co-host here when re-joining and letting the non host participant be a host is definitely not an option because it completely break what host / non host role and made for. What’s the point in transforming a non host into a definitive host, especially if the co-host do not have the right to unset this participant host power…
@nvivot @tommy definitely agree! The meeting host is who manage the meeting, allow people, mute/unmute them etc. if the algorithm assigns a random person, think about schools, if the teacher somehow loses the connection, that randomly assigned student can mess the meeting by adding friends or do other inappropriate things. Please provide a more safe solution to this issue
We appreciate the feedback. We are looking into a better solution. I will keep you updated on what we come up with.
we are waiting for a better solution for the problem
We will update you once we have a better solution!
I think we should close this thread. its been 2 months and the issue still exists.
This is an ongoing thread as we continue to work on the solution.
any timeline for this issue ??
1.8.1 released but the issue still exists? @tommy do you plan to resolve this Host remove issue seriously?
Correct, this was not fixed in the 1.8.1 release. It will be fixed in a later release.
I will share more details when I know which release.
We understand the sense of urgency and are doing everything we can to release this in a timely matter.
While there is a struggle with this bug, maybe you can suggest alternative solutions, imagine how now all teachers (hosts) can be blunt, leave by accident, a random student gets the host role, and that’s it. I would also be very grateful for the events on the SDK, which will be able to track all the user exits from the conference, whether it is closing a tab in the browser or rebooting or even turning off the light.
I try to store signature of host to my db, and when host loses his permission for example reload page, he is join to this meeting via signature which stored to db, but this is solution won’t return to host his permission, may be i do something wrong???
For tracking who leaves a meeting, including the host, you can use the Participant Left Meeting webhook.
To have the host rejoin as the co-host, make sure to set the role to 1 when generating their signature.
Teacher here. This is happening to me as of today. My temporary fix is to end the meeting and have students re-enter. Unwieldy but a possible interim path.