Zoom meeting starts temporarily and disappears

Meeting SDK
1

When I press a btn to start a meeting (using zak token), I see a zoom window pop up for a split second with the spinner going. It appears to say…waiting for meeting to start. But the video session doesn’t persist. The only error message I see in the browser is: error: TypeError: e.split is not a function. My front end setup is very similar to the React example your team provides with the React example. My React version is “react”: “18.2.0”. Will this be a problem?

I also noticed I get the same behavior whether I have a zak token or not! And when I don’t have a zak token, I don’t receive an error!

@chunsiong.zoom Any suggestions on trouble shooting?

2

@devontae can you try with react 16?
What version of the SDK are you using?

3

According to my package.json I’m using:
“@zoom/meetingsdk”: “^3.1.6”

4

@chunsiong.zoom I decided to clone your React example that uses an older version of React. But I’m receiving the following error for the code below:

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

I decided to simplify the original code so I could test.

function startMeeting() {
document.getElementById(“zmmtg-root”).style.display = “block”;

ZoomMtg.init({
  patchJsMedia: true,
  success: (success) => {
    console.log(success);

    ZoomMtg.join({
      signature: 1,//Because I want to simulate starting the meeting
      sdkKey: "I'm using my meeting sdk key here",
      meetingNumber: "I'm hardcoding a number from a meeting I generated on the backend via my node app",
      passWord: "hardcoded password from meeting generated on backend",
      zak: "I hardcoded this via a route (node.js) that creates a zak token for the same email that created the meeting",
      success: (success) => {
        console.log(success);
        return;
      },
      error: (error) => {
        console.log(error);
      },
    });
  },
  error: (error) => {
    console.log(error);
  },
});

}

5

@chunsiong.zoom I believe I found the issue. I was misunderstanding the signature value. I didn’t realize I needed to generate a signature on the backend first instead of hardcoding 1.

1 Like
6

Thanks for all your help @chunsiong.zoom :slight_smile: