Venkatesh Devale

Hi @kodai305 due to no activity I am closing this issue. Please feel free to re-open if you still have the same issue. Suggest checking out Sichao's solution above.

Thanks for the PR. Could you please update the description with a detailed issue, how the event is used and whats blocking to understand the change better? We also request...

Thank you for your interest in Amazon Chime SDK for JavaScript. I am not sure of a reason yet, but we have not tested the SDK on ubuntu for other...

Hi @vitiaaap29 sorry for the delay, but looks like there is no error in the provided logs from S22 ultra device. Could you please try once the below official WebRTC...

I tested on Chrome 98 Android 11 samsung device but could see the connectivity fine and the attendee could join the meeting fine. As mentioned by Trung above two things...

I see one meeting with Id: `1f5a330f-f09b-4a6c-b1cf-41affe7c0706` and two attendees in the attached logs: Attendee 1: `08c09264-f421-6c08-8d9b-037734b2a364` Attendee 2: `160d7267-4389-3f34-75a0-ae7ec87e957f` I think from the logs I see two issues happening:...

So first thing you have to fix is the multiple attendee issue. One meeting session is tied to only a single attendee and meeting response (meeting response can be shared...

Sorry for the delay in replying. From the [`CreateAttendee` public docs](https://docs.aws.amazon.com/chime/latest/APIReference/API_CreateAttendee.html) the `ExternalUserId` is an idempotent token. Thus, I believe it should return the same info in response. The second...

May be this was fixed in [`2.30.1`](https://github.com/aws/amazon-chime-sdk-js/blob/release-2.x/CHANGELOG.md#2301---2022-05-03). Have tagged messaging team for more help on this. Could you please check upgrading to `2.30.1` and whether that fixes it?

When you are using `amazon-chime-sdk-js`, the reconnection is handled internally so [`canRoconnect`](https://github.com/aws/amazon-chime-sdk-js/blob/release-2.x/src/messagingsession/DefaultMessagingSession.ts#L235-L243) decides the reconnection and you should be getting `messagingSessionDidStartConnecting` observer triggered when re-connecting. I believe in your case...