This message was deleted.

I might be missing something, but could it be possible that no

beforeunload

event is triggered with this codebase to disconnect from a room ?

hmm, this should be happening automatically as it's a function within our JS SDK: https://github.com/livekit/client-sdk-js/blob/main/src/room/Room.ts#L391 if it's not, it's probably a bug

In Next.js, because of how the routing is handled, I think there is a missing piece.

useEffect(() => {
    router.events.on("routeChangeStart", handleDisconnect);
    return () => {
      router.events.off("routeChangeStart", handleDisconnect);
    };
  }, []);

I had to implement the following. Id say this could probably be added to the LiveKitRoom Component or something similar.

that’s a good point. with the client side router the js sdk won’t pick up the route change. but as this is next specific, best we can probably do is supply a next specific helper method that does exactly what your workaround is doing. However we already try to disconnect on whenever <LiveKitRoom /> unmounts. this should also be happening on client route changes.

Id need to test some more without my implementation... one of the thing I was seeing is the delay from the other participants window.. still seeing that participant.. for the 10-15mins.. because that "disconnected" participant never sent out the disconnect message. I think this is where everything gets out of sync

1-15mins definitely sounds too long. the client will attempt to send the leave when dismounting, it’s not guaranteed that it will make it to the server. does the issue disappear entirely with your dicsonnect on route change workaround?

Yes, it is instant