The issue occurs when a RoomHandle is created and joined, another RoomHandle is created without joining, and then the first RoomHandle is closed. Any operations on the second RoomHandle (such as unmuteAudio or join) result in an error. This happens on both macOS and in the browser (during in-window calls). Currently, the error originates from the unmuteAudio method, but it will also occur from joinRoom if no other actions are taken.
Solution
This issue happens, because Jason has support for reusing one WebSocket for multiple Rooms, but it looks unsupported on the server side. It can be implemented, but this feature doesn't make too much difference, so best solution at this moment is just to create new WebSocket for each Room.
Synopsis
The issue occurs when a
RoomHandle
is created and joined, anotherRoomHandle
is created without joining, and then the firstRoomHandle
is closed. Any operations on the secondRoomHandle
(such asunmuteAudio
orjoin
) result in an error. This happens on both macOS and in the browser (during in-window calls). Currently, the error originates from theunmuteAudio
method, but it will also occur fromjoinRoom
if no other actions are taken.Solution
This issue happens, because Jason has support for reusing one WebSocket for multiple
Room
s, but it looks unsupported on the server side. It can be implemented, but this feature doesn't make too much difference, so best solution at this moment is just to create new WebSocket for eachRoom
.Checklist
k::
labels applied