There are a variety of scenarios that may prevent a user from being able to join a meeting. Below are some tips for finding the root cause of the issue.
What is the SDK saying?
The most useful troubleshooting tool for meetings in the SDK are the event interfaces. Similar to how IMeetingService is used to perform meeting actions, IMeetingServiceEvent is used to listen to the outcome of those actions. There are several event interfaces that will help with troubleshooting: IMeetingServiceEvent, IMeetingConfigurationEvent, IAuthServiceEvent, and IMeetingParticipantsCtrlEvent.
If you have attempted to join or start a meeting, but something unexpected happened, first check to see if the IMeetingServiceEvent callback onMeetingStatusChanged is being triggered. If it is being triggered, check the status it is reporting:
Another important event to listen for is the IAuthServiceEvent. This event has callbacks for authentication specifically. IAuthServiceEvent's onAuthenticationReturn callback reports the results of an authentication attempt:
What to do when callbacks aren't being triggered:
- Verify that the all the necessary DLL's are found by your application and that your project configuration properties are correct.
- Verify you have not only implemented the events above, but have set them by calling SetEvent on the relevant interface.
- An invalid JWT can prevent the callbacks from being triggered in certain versions of the SDK. Try your JWT in the demo app and if the same behavior occurs there, your JWT is invalid.
- Verify you are handling race conditions properly. The SDK must my authenticated before any SDK functionality can be called. Wait for the onAuthenticationReturn callback before trying to join a meeting.
- If you believe that a callback may be broken, please download and run the demo app that is included with the SDK package and verify it is broken there as well. From there, Zoom will be able to assist you on the developer forum.
What to do when the SDK is stuck at the "Connecting" screen or the "Waiting for host screen"
Issues like these usually stem for using tokens or links to join meetings. If you are running into this issue and are joining a meeting using a user token, ZAK token, or a link, try to narrow down the problem as much as possible.
- Is this happening for every meeting? If so, this is likely caused by how the user is being authenticated.
- Is this happening for every user? If so, this is likely caused by how the user is being authenticated or the settings of the meeting when it was created.
- Does this happen in the demo application as well? If so, this is likely caused by the settings of the meeting when it was created.
- Does this happen when joining with only a meeting number and password? If so, this may be a bug and Zoom will be able to assist you assist you on the developer forum.
What to do if you suspect a meeting link is causing issues
Most of the time, this is usually caused by how the API request was configured. Try using this same link in a Zoom application and compare the behavior to the SDK.
How to debug further?
If you still have not identified the issue, try to join a meeting under the simplest circumstances. Follow these steps:
- Start a meeting using the actual Zoom application on a separate device.
- On that device in that meeting, disable waiting rooms and any other feature that may complicate troubleshooting.
- In your SDK application code, hardcode that meeting's number and parameters in your join meeting params. Do not try to add a token or log the user in. The goal here is to get a simple guest participant into a meeting.
- Run your SDK application.
- If you successfully joined the meeting, try and add in additional factors and test again until you have identified what is breaking.
- If this did not work, follow the same steps using the demo application included with the SDK.
- If you are still facing issues, please reach out to Zoom on the developer forum or by email at firstname.lastname@example.org. Provide as much info as you can, the more the better.