-
Notifications
You must be signed in to change notification settings - Fork 477
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
Chime's reconnect behaviour causing AudioJoinedFromAnotherDevice? #2784
Comments
What happened and what did you expect to happen?Got AudioJoinedFromAnotherDevice errors on Electron as well. Have you reviewed our existing documentation?Reproduction stepsThe meeting started at 6:28 AM UTC, and the AudioJoinedFromAnotherDevice error was first received at 6:39 AM UTC. The device was locked during this time so there are lots of SignalChannelClosedUnexpectedly errors, but it isn't clear why the attendees rejoined. Amazon Chime SDK for JavaScript version3.18.0 What browsers are you seeing the problem on?Electron Browser version26.2.1 Meeting and Attendee ID Information.Meeting ID: 64dbad5e-39ac-4915-b393-d391610c2713
Browser console logs |
@hensmi-amazon @pracheth @dinmin-amzn Can someone please look into this? |
Any update on this issue? We are experiencing the same issue. |
Hey Team- Our customers are experiencing this issue quite often and support tickets keep coming in. |
Getting this issue after getting reconnected from meeting(more than 15 sec timeout i think). Issue only occurs for sdk versions > 16.0.0. |
Sorry for the delay. For now I will just revert that change so I can get it out in a release we have planned this week. Since I wish to eventually reroll that commit, can you clarify the experience? Were clients disconnected longer then they expected? Or were they just receiving that event unexpectedly. Did this occur while content was being shared? While video was being shared? I can see in the provided logs but any more patterns would be helpful. |
@hensmi-amazon Our clients share audio, video, and content. The issue occurs regularly, and can be caused by network errors due to actual connectivity issues or if they lock their device mid-meeting. |
Usually this happens when clients disconnected more than 15-20 sec. It occurs even without content sharing and video. A single audio attendee is enough to reproduce the issue. |
What happened and what did you expect to happen?
Got AudioJoinedFromAnotherDevice errors.
It seems to occur when we have SignalChannelClosedUnexpectedly errors due to network issues and Chime tries to reconnect.
Have you reviewed our existing documentation?
Reproduction steps
Not sure how to reproduce, but we're seeing SignalChannelClosedUnexpectedly errors due to network issues. Chime tries to reconnect but seems to sometimes cause AudioJoinedFromAnotherDevice errors. In the attached logs, it occurs at 14:08. I can share more examples as well.
Amazon Chime SDK for JavaScript version
3.18.0
What browsers are you seeing the problem on?
Google Chrome
Browser version
117.0.0
Meeting and Attendee ID Information.
Meeting ID: 862fffe2-c523-4c0b-8925-081764852713
Attendee IDs:
Browser console logs
ChimeMeetingLogs2.csv
The text was updated successfully, but these errors were encountered: