Joining meeting timeout issue in 1.7.5

Description
I am unable to join meeting using websdk 1.7.5 on WINDOWS 10 chrome version 80.

Error

  1. method: “join”
  2. status: false
  3. result: null
  4. errorMessage: undefined
  5. errorCode: 1

version?
websdk 1.7.5 chrome 80

To Reproduce(If applicable)
Steps to reproduce the behavior:
1.Use Meeting Id:***********
4. Password : 1234Anil

Screenshots

  • Browser:Chrome 80

Below is the code:

    var signature = ZoomMtg.generateSignature({
        meetingNumber: meetConfig.meetingNumber,
        apiKey: meetConfig.apiKey,
        apiSecret: meetConfig.apiSecret,
        role: meetConfig.role,
        success: function(res){
            console.log(res.result);
        }
    });

    ZoomMtg.init({
        leaveUrl: 'http://127.0.0.1:9999/index.html',
        isSupportAV: true,
        success: function () {
			console.log("hi");
			
            ZoomMtg.join(
                {
                    meetingNumber: meetConfig.meetingNumber,
                    userName: meetConfig.userName,
					
                    signature: signature,
                    apiKey: meetConfig.apiKey,
                    passWord: meetConfig.passWord,
                    success: function(res){
                        $('#nav-tool').hide();
                        console.log('join meeting success');
                    },
                    error: function(res) {
                        console.log(res);
                    }
                }
            );
        },
        error: function(res) {
            console.log(res);
        }
    });

*This post has been edited to remove any meeting / webinar IDs

1 Like

Hey @anilk
Please DM me your API Key/Secret and Zoom Account # and we will add you in the queue to get this resolved.

Why doesn’t the confirmation window exist in the web zoom sdk? It is very difficult for the user to discover that someone is asking for permission to enter the meeting.

Different account, same SDK version and same problem

Hey @anilk, @spaquet,

Please make sure you are passing in a valid meeting ID without dashes, and using a JWT App Key and Secret.

Thanks,
Tommy

Hey @daniel.vieira,

Thanks for the feedback, I will bring this up to the team.

Duplicate post:

-Tommy

Yes I do. but doesn’t work

Hey @spaquet,

How are you generating your signature? Please provide steps to reproduce the issue and your code.

Thanks,
Tommy

@tommy Hi I am using the app key and secret only and tried with meeting id without dashes. I am able to generate signature also. But the joining meeting is not working. if you check the code i have posted ablove. Can you please guide me, what the problem is whether my account or anything else.

Hey @anilk,

We believe this is a caching issue.

Can you please email developersupport@zoom.us with your JWT API Key so we can flush the cache manually to fix the issue.

Thanks,
Tommy

Hi @tommy ,
I sent JWT API Key details at developersupport@zoom.us . Can you check and let me know issue.

Thanks
Anil Kumar K

Hey @anilk,

Yes, we will work on fixing it asap.

Thanks,
Tommy

I am having this same problem. I am generating my signature on the server side with c#. What is this caching issue an can mine be cleared?

I have narrowed this problem for me to the provided C# code in the zoom documentation. It does not produce a matching SHA256 hash that the nodejs code produces. Does anyone have C# code to create the WebSDK signature server side that works?

Hi @jason,

Can you take a look at our signature sample code for c# and see if that works - https://marketplace.zoom.us/docs/sdk/native-sdks/web/essential/signature?

Also, make sure that your system settings are set to world time - Join meeting timeout or signature expired