Description
I couldn’t log into a meeting (not webinar) using my hosted Web Meeting SDK because of an error on the installation of “sdk-helper”
Browser Console Error
TypeError: Cannot read properties of null (reading 'postMessage')
at a.value (main.js?v=1.5.0.1811:1)
at aa (main.js?v=1.5.0.1811:1)
at vu (main.js?v=1.5.0.1811:1)
at t.unstable_runWithPriority (main.js?v=1.5.0.1811:1)
at Yo (main.js?v=1.5.0.1811:1)
at du (main.js?v=1.5.0.1811:1)
at tu (main.js?v=1.5.0.1811:1)
at Qa (main.js?v=1.5.0.1811:1)
at Fu (main.js?v=1.5.0.1811:1)
at main.js?v=1.5.0.1811:1
Which Web Meeting SDK version?
2.1.1
Meeting SDK Code Snippets
No customization, using the CDN folder sample app
To Reproduce(If applicable)
Steps to reproduce the behavior:
Thank you for posting in the Zoom Developer Forum. I reviewed the video but can’t reproduce that behavior on my end so I will need additional information. Can you share the meeting configuration set for that meeting? If the meeting is scheduled via API, please share the create meeting API request. This will help diagnose what may be happening.
Thank you for posting and calling attention to the behavior you are seeing. I’ve created an internal ticket to have this investigated further [ZSEE-37278]. More to follow as updates become available.
Before you getting an answer, can you just tell me if what I’m trying to do should be possible? Joining someone else’s meeting that requires login using the web SDK?
If it should be possible, I’ll wait, otherwise I have to change my plans now
Hi @donte.zoom! I was able to login with my localhost. But deployed version running under a URL won’t run it. Is there any special kind of configuration that I need to do related to my domain?
@donte.zoom Hi! Bumping this up. I’ve came to a way of replicating the problem, which is running the default repository with no modifications in the cloud.
What changes should I make to enable authentication when I deploy instead of running locally?
The authentication workflow should work the same when deployed. It seems like the behavior you are seeing may be related to your network firewall settings. When testing, be sure the appropriate inbound and outbound rules are set for the cloud provider hosting your Application. Down below, I’ve linked our Zoom network firewall or proxy server settings help documentation for reference:
I have found the solution. It is not proxy. The error that I’ve described in the first posted was about a postMessage method not being found in window.opener.
The window.opener is the browser instance that opened the window that was responsible for authentication. The opener was in my domain address and the authentication popup was in zoom’s address.
Because my Cross-Origin-Opener-Policy was set to same-origin, the browser respected that and didn’t fill in the window.opener for the Zoom popup.
The solution was setting up the Cross-Origin-Opener-Policy on my site so that it could accept the Zoom domain.
Glad to hear you were able to resolve the issue. I will pass this thread along to our documentation team for consideration. Perhaps we can make updates to our Improve Performance in Chrome help documentation. For other community members, please post the exact solution/resources that you found helpful. This will be of great help, and fellow community members will benefit significantly. I’ve linked related help documentation along with additional resources on that subject below.
will wait for the reply
