Recorder user couldn't join the meeting (realtimeSubscribeToAttendeeIdPresence was not triggered) in Chrome & Edge
See original GitHub issueWhat happened and what did you expect to happen?
What happened? I used the browser demo app
- I started the meeting and joined as a regular user
- And then I joined the meeting as a recorder user by appending record=true query parameter in the URL.
- Meeting Recorder attendee was not listed in the roster for both users (
realtimeSubscribeToAttendeeIdPresence
callback was not triggeed) - Also
attendeePresenceReceived
was not received for the recorder attendee
This issue was not occuring in Firefox browser. Occuring in Chrome & Edge browsers.
Expected result:
- When Meeting Recorder user joins the meeting,
realtimeSubscribeToAttendeeIdPresence
callback should be called and the recorder attendee should be listed in the roster.
Have you reviewed our existing documentation?
Reproduction steps
- Run the Browser Demo source code from aws-chime-sdk-js in hot-reload mode
- First start/join the meeting as a regualar user
- Then in a new tab join the meeting as a recorder user by appending record=true query parameter in the URL(http://localhost:8080/?m=Demo111&record=true)
- Now we can see that Recorder user was not joined in the meeting
Amazon Chime SDK for JavaScript version
2.17.0
What browsers are you seeing the problem on?
Chrome, Edge
Browser version
Chrome 93.0.4577
Meeting and Attendee ID Information.
No response
Browser console logs
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
amazon-chime-sdk-js recorder user couldn't join the meeting ...
amazon-chime-sdk-js recorder user couldn't join the meeting (realtimeSubscribeToAttendeeIdPresence was not triggered) in Chrome & Edge.
Read more >realtimeSubscribeToAttendeeIdP...
We are running into a weird scenario with Chime SDK. Scenario: User A joined and muted himself. Then User B joined, but User...
Read more >Why can I join a Teams meeting on Chrome but not on Microsoft
A customer I'm working with asked me to join a Teams meeting, it wouldn't open in the Teams App for windows or in...
Read more >Issues joining a RingCentral Video Meeting using browsers ...
This article provides instructions on how to resolve the issue when users are unable to join a meeting on RingCentral Video on web...
Read more >Cisco Meeting App WebRTC Important Information
You can use WebRTC app with Firefox 80 and later. Versions earlier than 2.9.4 are not supported on Firefox 80. 1.2.2 Microsoft Edge...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @vishnusankarkrishnan , thanks for bringing this up. I can reproduce this issue in Chrome, Edge and Safari. The issue seems related to autoplay policy. By enable the autoplay policy for the site, the issue is gone. We will look in this issue to figure out the rootcause. Could you please try the below steps to avoid this issue for now?
Let us know whether this helps. Thanks!
Hi @vishnusankarkrishnan, we got a same issue #1715. We find the recorder is blocked by the AutoPlay policy. So instead of enable the AutoPlay policy like we mentioned earlier, you could add some interaction to let it pass the AutoPlay policy. For example you could add a join button when the URL contains
record=true
and then the recorder could join the meeting after clicking the button.