Hi all,
we are integrating the websdk package into our Angular 15 app
Below the Meeting SDK type and version we’re working:
Meeting SDK 2.9.7 component view
We have a problem when the meeting starts after the user tries to join.
The user clicks join and receives the message ‘Meeting has not started’
Then the user close the window by clicking on the red button.
When meeting starts , user clicks on Join Meeting again (without refresh the page).
It seems that the join was successful, but no windows open.
The meetingSDKElement view is empty.
@it17,
Thank you for posting on the Zoom Developer Forum and sorry for the missed response. I see you are using the Meeting SDK 2.9.7 component view and have a problem when the meeting starts after the user tries to join. I’ve seen reports of similar behavior in the past where clicking on join the meeting again without refreshing the page causes unintended behavior. We recently introduced an API to destroy the Component View client to allow re-creation from scratch. Here is the link to the changelog and the Component View documentation for your reference:
DestroyClient Changelog
destroyClient
When attempting to rejoin meeting without refreshing the page, can you try the following approach:
Upon leaving, destroy the client.
When returning back to the angular page/component, create the client and initialize again.
Hi @donte.zoom and thanks for your reply. Unfortunately this function doesn’t seem to be presente at the links you posted. A full search on google and GitHub has just showed this reference
in meetingsdk-web/embedded.d.ts at master · zoom/meetingsdk-web · GitHub.
Could please point us to some link where we can find some little documentation, or just drop two lines of code, to understand how in the context of the angular component, we can destroy the client?
Thanks in advance
Hi Dante,
thank you for reply.
just to avoid any iincomprehension, I would like to remember that we are in a SPA Angular app. This means we never leave the page. We try to join the meeting, we receive an error. So, we remain inside the same component, and code doesn’t get reinitialized.
We thought about checking if the meeting is started before joining it, but in our context which is interactive, webhook doesn’t fit.
So in order to avoid unexpected behavior, every time client join fails,
we destroy client, we recreate and initialize it again:
Thank you for sharing these additional details. I believe this is related to a known issue that our Engineering team is working to address [Z-475406]. Please make sure to subscribe to our blog, change log, and developer guides topics for the latest news, updates, and fixes. You can also find Announcements here :