Open endel opened 2 years ago
Hi Any update on this issue? even we are also facing the same issue
Hi, I am facing the same issue as well. Using an android build to test Steps :
PS: in the server's onLeave method, have added code to allow for reconnection
@AbhishekFYND Do you possibly have a small project where we can observe this problem? Do you also use the reconnection feature?
@nuruddinwarsi How does your onLeave()
method look like? I've seen some people using .allowReconnection()
without the await
keyword, thus having unexpected behaviour
@endel
try { if (consented) { throw new Error(Player ${leavingPlayer.id} consented ); } // 10 sec allowed to reconnect await this.allowReconnection(client, GameRules.ReconnectionTime); leavingPlayer.assign({ connected: true, readyState: PlayerReadyState.READY, }); } catch (ex) { // code to remove player from state and declare winner }
I have few concerns regarding my connection flow as well. Server is using typescript / Node and client using Unity / C#
Is there a difference between using client side vs server side joinById method?
Reported by @rakeshparihar on https://github.com/endel/NativeWebSocket/issues/61