Can join the meeting but cannot enable video and audio on a global https server (we can enable them on the localhost)

Hi everybody,

I’m building an app using zoom web sdk.

It is working well on the localhost (http://localhost:4200/).

But some problems occur on the global server (
With a url that looks like https://example.net).

We only can join but can not enable Video and Audio.

We serve it by https.

This is a screenshot( (I erased private information).

Even if you can’t read Japanese, you can see that you can’t enable the microphone and video.

On the global server I got the following error on the console:

ready to start!
ready to start!
ready dec video!
CompileError: WebAssembly.instantiate(): expected 24076271 bytes, fell off end @+13
ready dec video!
CompileError: WebAssembly.instantiate(): expected 24076271 bytes, fell off end @+13
CompileError: WebAssembly.instantiate(): expected 24076271 bytes, fell off end @+13
CompileError: WebAssembly.instantiate(): expected 24076271 bytes, fell off end @+13
CompileError: WebAssembly.instantiate(): expected 24076271 bytes, fell off end @+13
CompileError: WebAssembly.instantiate(): expected 24076271 bytes, fell off end @+13

I am using zoom web sdk version 1.8.0.
And the browser I’m using is chrome 85.0.4183.121 (Official Build) (64bit)

Hey @kensaku_tanaka,

Have you allowed the browser to access your video? Are you still seeing this issue?

CC @yosuke.sawamura.

Thanks,
Tommy

thank you for answering, @tommy.

If I serve the app from localhost, I can access my video. But I cannot access my video If I serve same app from global server via https.
And compile errors of WebAssembly occur only in global server.

Hey @kensaku_tanaka,

That is strange. Is there a way you can give me access to test this on your global server? If so, please email instructions to developersupport@zoom.us, and include a link to this thread.

Thanks,
Tommy

Hi. tommy.

Thank you for your reply. And sorry for the late answer.
I have already solved this problem.

It was a cache issue.
After clearing all the chrome cache, the problem disappeared.
Perhaps the cache of the previous version of the sdk remained.
Clearing the cache from the chrome developer tool didn’t work, but clearing the page cache from the chrome settings screen worked.

Thank you for your support.

Hey @kensaku_tanaka,

Thanks for following up and letting us know. Glad it’s been resolved :slight_smile:

Best,
Will

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.