<@U084APK40NS> what are the types of disconnect re...
# ask-ai
r
@millions-hair-24956 what are the types of disconnect reasons in client sdk javascript/js ?
g
In the LiveKit Client SDK for JavaScript, disconnect reasons are not explicitly listed in the provided data sources. However, the DisconnectReason enum in the Flutter SDK provides a list of possible reasons, which might be similar across different SDKs. These include
unknown
,
clientInitiated
,
duplicateIdentity
,
serverShutdown
,
participantRemoved
,
roomDeleted
,
stateMismatch
, and
joinFailure
. Would you like more detailed information on how these reasons might be used or handled in the JavaScript SDK? Sources: - DisconnectReason enum πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @runllm in the thread for followups.
r
@millions-hair-24956 that’s the flutter sdk. I want the enum in javascript sdk (client-sdk-js)
g
The specific disconnect reasons for the JavaScript SDK are not explicitly listed in the provided data sources. However, the RoomEvent.Disconnected event in the JavaScript SDK can be triggered by reasons such as
DUPLICATE_IDENTITY
,
PARTICIPANT_REMOVED
, and
ROOM_DELETED
, as mentioned in the documentation. Would you like more detailed information on handling disconnections in the JavaScript SDK? Sources: - RoomEvent.Disconnected πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @runllm in the thread for followups.
r
@millions-hair-24956 the sdk will not try to reconnect on its own automatically after this right?
g
Correct, the SDK will not automatically attempt to reconnect after a
Disconnected
event due to reasons like
DUPLICATE_IDENTITY
,
PARTICIPANT_REMOVED
, or
ROOM_DELETED
. These are considered unrecoverable disconnections, and manual intervention is required to reconnect. Would you like more details on how to handle reconnections manually? Sources: - https://livekit-users.slack.com/archives/C07FVFGAUKX/p1730865908.353019 - https://docs.livekit.io/client-sdk-flutter/livekit_client/RoomReconnectingEvent-class.html πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @runllm in the thread for followups.