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…