Unavailable audio with an event named receivingAudioDropped

[MohammedTaha]

What are you trying to do?

Trying to fix an state where users (just got connected with meeting, can see each other means video is getting transmitted without any problem) are unable to hear each other with this event named receivingAudioDropped

How can the documentation be improved to help your use case?

Please suggest the possible actions I shall take in order to

• Avoid this issue
• Reconnect the audio once I receive this event

What documentation have you looked at so far?

So far I've tried to read the SDK Developer guide, specially this section and other general forums. The developer guide mentions this event but wasn't really helpful in term of resolving this error.

Also sharing the meeting history array if this can be used to determine any possible mistake

 "meetingHistory": [
    { "name": "videoInputSelected", "timestampMs": 1645614909311 },
    { "name": "audioInputSelected", "timestampMs": 1645614909378 },
    { "name": "meetingStartRequested", "timestampMs": 1645614909380 },
    { "name": "meetingStartSucceeded", "timestampMs": 1645614915193 },
    { "name": "attendeePresenceReceived", "timestampMs": 1645614917571 },
    { "name": "receivingAudioDropped", "timestampMs": 1645614927387 }
  ]

[devalevenkatesh]

@MohammedTaha Thank you for reporting this issue. This receivingAudioDropped event is triggered when the Amazon Chime SDK for JavaScript (JS SDK) sees that there is not enough bandwidth and is experiencing connectivity issues. When SDK sees that the connection is good you should be able to connect back fine and there is no handling required from builders to connect the audio back.

So couple of questions:

1. Could you please check guide on connectivity and implement connectionDidBecomeGood and connectionDidBecomePoor observers so that you know when the connection is back up fine and then see if the audio is working as expected.
2. What is the JS SDK version you are using?
3. Is this issue cross-browser? Also request to add browser versions and console logs to check.

[MohammedTaha]

@devalevenkatesh, thanks for the prompt response.

I'll add these observers and see if it can help in delivering better experience. Let me also try to answer your questions
1 - On me, I'll add them and see if audio gets available as soon as connectionDidBecomeGood gets triggered. Assuming its just the network bandwidth issue, I think the video streaming should also get impacted while its not the case in most of my observations.
2 - 2.26.1
3 - Yes, observed this issue atleast on Firefox, Brave and Google Chrome. I mostly use Google Chrome - Version 98.0.4758.102 (Official Build) (x86_64) for development purposes and found this happening like 1 out of 3 times.

[devalevenkatesh]

We have fixed a reconnecting issue in 2.27.0 but not sure if this is the same issue you are observing. Can you also try to upgrade to 2.27.0 and see if the re-connection also gets better?

[nainkunal933]

Closing this issue due to inactivity. Please feel free to reopen if you still need help.