Description
While using the Zoom Meeting SDK for web we are running into an issue when our users are using a waiting room for their meeting.
The issue is shown slightly differently if I use the Client View vs. using the Component View.
If I use the Client View, the application will get stuck into the join meeting as shown in this screenshot:
If I use the Component View, the application will successfully join the meeting but I will never ever get audio.
How to reproduce the issue
This is a timing issue as you have to admit the user into the meeting before the WebSDK is actually in the “lobby”.
Simply clicking on this button:
before the user sees either the “The host will let you in soon” for the Component View or the entire lobby for the Client View.
This is not easy to reproduce when you are using a very powerful computer with production bundles, but I managed to reproduce it with the GitHub - zoom/meetingsdk-web-sample: Zoom Meeting SDK web sample on a Mac Book Pro from last year with an M1 Pro Max CPU.
To make it very easy to reproduce, I suggest to test on a lower power device such as a Chromebook and a DEV bundle. that way you have can have 2 to 3 seconds to click the admit button before it is too late.
Browser Console Error
There are no specific error messages that seems to stand out. Some error messages are indeed present but they are also when I click the admit button after everything is setup and everything works.
Which Web Meeting SDK version?
2.17.0
Meeting SDK Code Snippets
I used the sample I linked above.
Troubleshooting Routes
I tried all kind of things, but I haven’t found ways to fix it. It seems that the js_media initialization is not finished while I am already “allowed” in the meeting which leads to the issue but since we are using a bundled version, it is very difficult to say.
Device (please complete the following information):
I reproduced it on a MacOS M1 Pro Max, an Ubuntu 22.04 with a threadripper CPU and other lighter computers. All using Google Chrome.