Thank you for posting in the Zoom Developer Forum. It appears that you have encountered an issue with an older version of the Web SDK. Could you please try using the latest version of the SDK and let us know if the problem persists? Each release includes numerous bug fixes, so testing with the updated version will help determine if this behavior has already been addressed.
Please see our change log for the latest update and changes :
I have already updated the SDK version to the latest version 2.16.0, but it seems that the problem is not with the Zoom Meeting SDK. In our application we are using both Zoom SDK and Contact Center SDK and as I described earlier the problem is with video-client.js (you can find the exact point and error in the screenshot) and after updating the Zoom Meeting SDK it still present.
Thank you for your response. I have reviewed the screenshot provided, but it does not contain enough information to diagnose the issue. I have a few follow-up questions:
Can you share a screenshot of all the logs? This will help me understand the complete context.
Does this issue occur when you run the app separately, or is it specific to integration?
At what point does Safari block all mobile clicks? Is this issue specific to Safari?
How have you tested this behavior on different browsers?
Which button is clicked to trigger this behavior?
Please provide the additional information so that I can assist you further.
2. Does this issue occur when you run the app separately, or is it specific to integration?
Issue occurs when I run app separately
3. At what point does Safari block all mobile clicks? Is this issue specific to Safari?
It blocked when I visit a page with several “Contact Centers” on the moment when app trying to get new instance of video client by executing new VideoClient({});. When I commit this string, error disappears and click events start working. Issue specific for iOS and can be reproduced also in Chrome.
4. How have you tested this behavior on different browsers?
Just install another browsers (Firefox, Chrome) and try to open necessary app page.
5. Which button is clicked to trigger this behavior?
I see that you have a support ticket regarding this matter. It appears that the root cause may be related to how the website elements were modified on the page with multiple “Contact Centers”. Is the same behavior occurring when the website elements are not modified? Also, what happens if you visit a page with only one contact center, does the same behavior occur? I am looking to better understand at what point same the page and what edge cases have you tested and explored.
Also, could you please elaborate on what you mean by “the SDK connect to framework”? Specifically, which framework are you referring to when connecting the SDK?
@victor.softeq ,
We understand that this matter is urgent and are currently working to gain a better understanding of how to proceed. Your use case is unique, which requires us to comprehend the user experience you are aiming to achieve and how you are implementing the Video SDK. Please know our engineering team has been collaborating with support to assess and offer guidance. We appreciate your feedback and patience on this matter.
Sorry, I’m not sure I understood you correctly in this case. We have a page with list of “Contact centers”. Basically it’s a grid with buttons to join and additional text information about each room. We get this list from BE, so when the user comes to this page, it is empty and all the data appears a little later.
Yes, it doesn’t matter how many centers are displayed.
