This message was deleted.

hm, I haven’t seen this before. under what circumstances does this issue appear? Is there a way to reproduce it?

Also while testing we are observing that if a remote participant leaves call by calling room.disconnect instead of 1. handleParticipantDisconnected it calls 1. handleTrackUnsubscribed 2. handleParticipantDisconnected however in handleTrackUnsubscribed,

room.participant.get(sid)

returns null.

the second issue you are describing got fixed already in livekit-client v1.9.6