Great questions
The SDK can perform UI operations in your application. Anytime this happens, it should be on the main thread as UI updates should never be performed on a background thread. This doesn’t necessarily mean that all of the SDK related functions need to be on that thread, but if there is even a possibility that a certain function will update the UI in some way, it should be called from the main thread. Something like joining a meeting should not happen on a background thread as it shows the meeting UI. Something like initing the SDK could, however, you need to be conscious of race conditions. The Zoom SDK “events” should help to guide your threading logic.
I’m a little confused. I’m trying to use some functions in tasks and because of this, some events stopped working (But when I do not use tasks, everything works well)
For example, I describe the situation.
I call the PutInWaitingRoom() function in the task.
waiting room enabled
The host creates a meeting.
The participant connects to the meeting and enters the waiting room.
The host sees this event that a new participant has connected to the waiting room.
The host invites the participant to the meeting.
The participant joins the meeting.
The host sees the event that a new participant has connected.
The host transfers the participant to the waiting room. 8. The host does not receive the event that the participant has appeared in the waiting room (OnWatingRoomUserJoin).
If a new participant joins the meeting, the host’s OnWatingRoomUserJoin event is triggered. It doesn’t work just after the PutInWaitingRoom button has been pressed.
This event does not have access to the GUI. And there are no errors. All functions return “SDKERR_SUCCESS”.
With what it can be connected?
What am I doing wrong?
Hmm that is indeed strange. I do not believe this is caused by a threading issue and this may just be a bug with the waiting room functionality. Can you provide the SDK version number you are using?