-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: "could not find participant" when a participant quickly reconnects #451
Comments
which version of the SDK are you using? Can you share specific steps to reproduce the issue? |
@davidzhao Here's code example for Go Server:
I also can provide code for iOS client. But the steps are:
Here's log I get for the code above:
|
As long as it prints Probably what's missing is a call to |
@dennwc Hi! Do you have any progress on this? |
Thank you for the ping, I didn't check it yet. I'll try testing it this week. |
@dennwc Could I help you with something to reproduce the issue? |
@dennwc Hi! Still no updates? |
I have an instance of the Go Server SDK that monitors a room. Also, I have iOS client apps that connects to a LiveKit media server.
If an iOS client force disconnects from LiveKit server (like by force killing client app process) and reconnects after a few seconds before LiveKit media server emits a "participant disconnected" message due to timeout then Go LiveKit Server SDK fails with error like:
"msg"="could not find participant" "error"=null "participantID"="PA_2rjapiiKp9hi"
on media track publication by this iOS client.The error message comes from
room.go: handleMediaTrack
function.Probably, it's because of no "participant connected" event is fired when the client reconnects for the second time before the timeout ends.
The text was updated successfully, but these errors were encountered: