API Endpoint(s) and/or Zoom API Event(s)
<link type=“text/css” rel=“stylesheet” href=“https://source.zoom.us/2.7.0/css/bootstrap.css” />
<link type=“text/css” rel=“stylesheet” href=“https://source.zoom.us/2.7.0/css/react-select.css” />
<script src=“https://source.zoom.us/2.7.0/lib/vendor/react.min.js”>
<script src=“https://source.zoom.us/2.7.0/lib/vendor/react-dom.min.js”>
<script src=“https://source.zoom.us/2.7.0/lib/vendor/redux.min.js”>
<script src=“https://source.zoom.us/2.7.0/lib/vendor/redux-thunk.min.js”>
<script src=“https://source.zoom.us/2.7.0/lib/vendor/lodash.min.js”>
<script src=“https://source.zoom.us/zoom-meeting-2.7.0.min.js”>
Description
When I tried to migrate the zoom websdk from 2.6.0 to 2.7.0, I have updated the meeting.html and meeting.js (from 2.6.0 to 2.6.7) and changed apiKey to sdkKey.
I am using iFrame to embed the meeting.html, the iFrame src is also updated to pass the sdkKey, instead of apiKey.
Of course, I also updated the JWT api key and secret to Server-to-Server OAuth.
But I still use the old function to generate the signature, not sure if this is the reason causing the error.
Error?
The video screen shows:
Joining meeting timeout
invalid parameter
How To Reproduce
Steps to reproduce the behavior:
Here is the generated link for iFrame
vendor/zoom/CDN/meeting.html?name=xxxxxxxxx&mn=/8869354886&email=xxxxxxxx=&pwd=322185&role=0&lang=en-US&signature=aEwybTBiTDFUMDJzX2xvSlFiZ0JKZy44ODY5MzU0ODg2NS4xNjc4NzYxNTY0MDAwLjAuMjVZZ2YvcXh5dEw0amtOeDRDbE5EOGhKRkk3bzBjanh5NjAwMDIxejhMMD0&china=0&sdkKey=hL2m0bL1T02s_loJQbgBJg
@nelson.chow.
Thank you for posting in the Zoom Developer – I am happy to help. See response below:
It looks like you the mn parameter has / appended to the meeting number. Can you removed that / and let us know if the behavior persists ?
Actually, there is no “/” between “mn=” and the meeting ID in the source code, not sure why it shown the “/”. Anyway, I tried again, still same error
/vendor/zoom/CDN/meeting.html?name=Ui0yMTE2MTM2&mn=87092947942&email=Ui0yMTE2MTM2QGhpZGRlbi5tcHBsaWNhdGlvbi5jb20=&pwd=553455&role=0&lang=en-US&signature=aEwybTBiTDFUMDJzX2xvSlFiZ0JKZy44NzA5Mjk0Nzk0Mi4xNjc5NDUzMjE3MDAwLjAuWkdzSmdJM2JrUEFUQW9zY2J6Qnc3ZzNRSVlFLy8vbWZlTDY3eDZ6b2JHdz0&china=0&sdkKey=hL2m0bL1T02s_loJQbgBJg
Thanks for your response, @nelson.chow! Are you seeing the same issues with our Demo app? Or just with the migrated Zoom Web SDK version of your app? If the former, could you provide the steps to reproduce this with our demo app?
I have not checked your demo app. I just upgrade on my own codes at this stage. Do you mean I need to use your demo app to rewrite all the things?
Can I modify my existing codes in order to upgrade?
@nelson.chow,
You can modify your existing codes in order to upgrade but you may encounter nuances. To help isolate the behavior you are seeing, could you please test with the sample App and let us know if the behavior continues?
Sorry, could you tell me where could I find the sample app?
@nelson.chow,
You can find all of our sample Apps on Github: Zoom · GitHub
@nelson.chow,
Instead of entering your client ID and secret (Server-To-Server OAuth), you want to enter the Meeting SDK marketplace App client ID and secret.
Create a Meeting SDK App
https://marketplace.zoom.us/docs/guides/build/sdk-app/
Authorization (Meeting SDK )
https://marketplace.zoom.us/docs/sdk/native-sdks/auth/
Note :
