Description
Hello,
I had an issue implementing the Meeting SDK for web recently, and @donte.zoom was really helpful with some extra debug steps I want to outline here.
I had a set up combining the default API with the Meeting SDK. I had the ability to create and delete meetings, and was working on the ability to join a meeting from inside my UI using the client.join() method when I encountered error 3265.
This error states something like “Token not allowed” - it’s kind of awkward wording, I think it’s just the default error code for the client.join() method.
What you would assume you should do when encountering this error is confirm that your signature is being composed correctly, and generally feel lost when you determine that it is correctly generating the signature JWT.
My specific issue was that my “create meeting” call was also creating a password for that meeting, and I was failing to pass that password forward to the client.join() call.
3265 is an inappropriate error code here, I’d expect a message like “password missing” rather than “token not allowed.”
Basically, if you encounter 3265 when using the Meeting SDK, you have to inspect more than just your JWT construction for the signature field.
Which Web Meeting SDK version?
3.11.2
Meeting SDK Code Snippets
// this is JSX for SolidJS, client(), signature(), user(), and zoomMeeting() are Solid Signals (like React's useState) where calling the function returns the current value.
// client() is declared as so:
const tempClient = ZoomMtgEmbedded.createClient();
const [client, setClient] = createSignal(tempClient);
// this snippet is called after client(), signature(), user(), and zoomMeeting() are populated correctly
client().join({
sdkKey: import.meta.env.VITE_ZOOM_SDK_KEY as string,
meetingNumber: zoomMeeting()?.id! + '',
userName: user()?.name!,
signature: signature(),
password: '', // <= My issue was here :3 I didn't realize my meetings had passwords attached
tk: '',
});