Description
I started getting errorCode: 3008, errorMessage: “Please init meeting first!” even though I am initializing my meeting and the exact same code was working on @zoomus/websdk@1.7.10
Error
Console output prior to the error:
13:24:10.918 zoomus-websdk.umd.min.js:formatted:1 Zoom support you browser. Chrome/85.0.4183.83
13:24:10.918 zoomus-websdk.umd.min.js:formatted:1 You browser support below features
13:24:11.467 Zoom.jsx:50 {method: "init", status: true, errorCode: 0, errorMessage: null, result: null}
13:24:11.649 zoomus-websdk.umd.min.js:formatted:1 pre load wasm success: /zoom/lib/av/5628_audio.encode.wasm
13:24:11.751 zoomus-websdk.umd.min.js:formatted:1 pre load wasm success: /zoom/lib/av/5628_video.mt.wasm
13:24:11.766 zoomus-websdk.umd.min.js:formatted:1 pre load wasm success: /zoom/lib/av/5628_video.decode.wasm
13:24:11.777 zoomus-websdk.umd.min.js:formatted:1 pre load wasm success: /zoom/lib/av/5628_video.simd.wasm
13:24:12.468 zoomus-websdk.umd.min.js:formatted:1 {method: "init", status: false, errorCode: 3008, errorMessage: "Please init meeting first!", result: null}
We’re happy to look into this for you. As a first step, can you provide your web SDK code snippet, or a Github repo link? This will help us to debug on our end.
Thanks for getting back to me with your sample—after taking a quick look, I would recommend moving the following lines to immediately follow your import statements:
ZoomMtg.setZoomJSLib('/zoom/lib', '/av') // I made the lib available in the public folder
ZoomMtg.preLoadWasm()
ZoomMtg.prepareJssdk()
While this is not exactly the same, you’ll notice in our Angular sample app a similar approach:
It’s likely this will do the trick, but let us know if not!
Tried it. That specific error stopped. But now nothing happens after loading the /av files:
I tried using our local copies with ZoomMtg.setZoomJSLib('/zoom/lib', '/av') as well as source.zoom.us, with ZoomMtg.setZoomJSLib('https://source.zoom.us/1.8.0/lib', '/av') to the same result. Nothing happens after loading the /av files…
There are console.log inside both init and join success callback functions and there are console.error inside both init and join error callback functions. This is all the output I get:
19:43:15.009 zoomus-websdk.umd.min.js:2 Zoom support you browser. Chrome/85.0.4183.83
19:43:15.011 zoomus-websdk.umd.min.js:2 You browser support below features
19:43:15.716 zoomus-websdk.umd.min.js:2 pre load wasm success: /zoom/lib/av/5628_audio.encode.wasm
19:43:15.796 zoomus-websdk.umd.min.js:2 pre load wasm success: /zoom/lib/av/5628_video.decode.wasm
19:43:15.883 zoomus-websdk.umd.min.js:2 pre load wasm success: /zoom/lib/av/5628_video.simd.wasm
19:43:15.904 zoomus-websdk.umd.min.js:2 pre load wasm success: /zoom/lib/av/5628_video.mt.wasm
I also tried the same thing (moving those 3 lines to immediately follow the import statements) with the version that was working (1.7.10) and the behavior was the same. After loading the /av files nothing happens. So I don’t think that the problem is the position of those lines…
You’ll have to replace the part where the app access /api/v1/autenticar/zoom/${this.state.meeting.meetingNumber} to get the apiKey and signature, because that part is not available in that code.
The app homepage is located at /zoom and the meeting info is retrieved via query parameters
Sample URL:
passWord is optional (the code assumes passWord='' when not informed
That’s because the map file for the JS is not available. (webim.min.js.map)
Even when we use ZoomMtg.setZoomJSLib('https://source.zoom.us/1.8.0/lib', '/av') that happens.
Even when using 1.7.10 that happened.
That is not the problem. That’s a warning stating that the browser couldn’t find the map file for webim.min.js and that’s simply because you guys don’t provide a map file for your minified javascripts.
Like I said. That’s a warning. That does not stop the code from running.
The trouble you’re having is exactly the trouble I was having after I did what @will.zoom instructed here (Moving setZoomJSLib, preLoadWasm and prepareJssdk to immediately follow the import statements)
After the page loads the wasm files, nothing else happens.