I’ve installed the sample application (https://github.com/zoom/sample-app-web) to understand how I can integrate the site I’m developing with zoom.us meetings. I’ve changed url of JS-API to correct https://source.zoom.us/zoom-meeting-1.2.4.min.js and write my API keys to index.js. I started a meeting with zoom desktop program, and join it with the sample application in my browser (the newest Google Chrome). It didn’t show any errors in browser’s console, but also I didn’t see any video in the browser. I see only participants of the meeting. http://prntscr.com/jny5v6. But if I use https://zoom.us/wc/join/xxxx, I see my video. Why it can be? What I can do with it?
Currently our sample web app does not support the video camera feature only audio. We are currently looking into to see when we can update it to support camera functionality.
We plan on supporting the camera feature in our August release. We’ll keep the development community informed about any other enhancements.
Did this ever get fixed? Does “https://github.com/zoom/sample-app-web” do anything useful? I get a big blank white screen with “Name”, “Meeting ID”, and “Join”, and no errors, even after changing the key and secret. Entering various possibly valid and definitely bogus values into these boxes and clicking Join produces no result, but also no error. The big, blank, white area remains big, blank, and white. Reloading in the debugger reveals little; an API call is being made, and it does not appear to fail, but that’s all I can tell.
What EXACTLY, PRECISELY should that application do?
Demo / reference applications need to be STRICTLY documented. People will be comparing their work to those to have confidence that they are using your APIs properly. Right now this is embarrassing me to a client.
I have had to change the port from 9999 to something real for firewall reasons.
Does this app require HTTPS, even though it is a test app and I’m using throwaway keys? Do I really have to let testing this overlap with SSL configuration? If so, was any provision made to supply a certificate to that app?
Wait, I see the problem now. Use any name for “Name”, and use your Personal Meeting ID for a test meeting-- HOWEVER, be sure you strip the dashes out of the meeting ID.
That’s really bad. The fact that you have any developers AT ALL that fail to sanitize user input for any reason EVER, let alone in a reference application, does not fill me with confidence that your servers and databases are written to any higher standards. Your sample applications should show off the very best code you can write-- or developers will assume they ARE the very best code you can write.
Worse, this failure provides no feedback of any kind, so it isn’t clear whether the client has failed, the server has failed, or the user has provided bad input.
Whoever wrote this should not be allowed to write its replacement, and that replacement should be done right quick.
Oh, and in any case, for anyone else finding this-- yes, as of 19SEP2018, the video is still broken/missing/unimplemented.
The issues with video were fixed as of our JS 1.3.0 release last month.
The Sample Web App is a sample that designed to show users how to join existing Zoom meetings over the web by entering your name and Meeting ID. Currently, our Sample web app offers 2 way audio/video, Voice over IP, and Multi-lang feature.
For more information please check out our docs - https://devdocs.zoom.us/docs/zoom-sdks/Web-Client-SDK and SDK Docs - https://zoom.github.io/zoom-sdk-web/ZoomMtg.html#init.