in the basic example, we experience very often, that if couple of users have joined in the conference (non mixed mode) and everybody see's each other, then a new user joins, in the JOIN callback, it returns 1 user (self) and 0 streams, so it's not able to subscribe to any of the existing user's streams.
Usually we need 1 or 2 page refreshes and then it works.
Do u know why and what might be causing this issue?
unfortunately we don't see any client side nor server side errors.
However, we have implemented a "RETRY" workaround on the client side with JS promises, that retries up to 10 times with certain delay the following three steps:
if the join callback returns only 1 user and 1 stream. In other words for the first member to a conference always goes via this 10 trials and for every other new participant to the conference, usually 2-3 retrials are enough to successfully join.
Currently this works well enough for us. But if you can identify why this is happening so that we avoid using this workaround, it would be really helpful.
Thanks for your info. We have found the clue on the issue of cluster components keeping disconnect and connect from cluster manager under some special environments and fixed internally. It will be included in next major version around early Jan. Feel free to let us know if you need a patch to check whether that helps your case.