Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin has stopped working #6

Open
worthiejones opened this issue Mar 11, 2021 · 13 comments
Open

Plugin has stopped working #6

worthiejones opened this issue Mar 11, 2021 · 13 comments

Comments

@worthiejones
Copy link

This plugin is no longer working correctly. I would be glad to send you the error information, if you are still supporting it.

Thanks

@michaelbourne
Copy link
Owner

Please do!

@worthiejones
Copy link
Author

worthiejones commented Mar 11, 2021 via email

@michaelbourne
Copy link
Owner

The error says Webinar 94549576291 not found or expired. are you sure that was the right code?

@worthiejones
Copy link
Author

worthiejones commented Mar 11, 2021 via email

@oregondean
Copy link

FWIW, I am a new user and it is working for me.

@apos37
Copy link
Collaborator

apos37 commented Apr 19, 2021

I have a developer account that I set up the API on, and another account for testing registration from a different account. When I set this up with your directions, it works fine for me. HOWEVER, when I try to use a webinar code from a client's account, I keep getting the same error as shown above. I compared the two meeting settings side by side and everything is exactly the same. Is there something that might be causing this?

@oregondean
Copy link

I have a developer account that I set up the API on, and another account for testing registration from a different account. When I set this up with your directions, it works fine for me. HOWEVER, when I try to use a webinar code from a client's account, I keep getting the same error as shown above. I compared the two meeting settings side by side and everything is exactly the same. Is there something that might be causing this?

Are you using the client account login info when you try to access their meeting info?

@apos37
Copy link
Collaborator

apos37 commented Apr 19, 2021

What do you mean? I had the client log in to their account while sharing their screen and I logged into mine to verify the meetings were set up the same. As far as set up goes, I'm using the same API key and API secret from my developer account. I thought maybe they would need a developer account initially, but I tested just entering a webinar code from a different account we have and it worked flawlessly.

@oregondean
Copy link

What do you mean? I had the client log in to their account while sharing their screen and I logged into mine to verify the meetings were set up the same. As far as set up goes, I'm using the same API key and API secret from my developer account. I thought maybe they would need a developer account initially, but I tested just entering a webinar code from a different account we have and it worked flawlessly.

You cannot access anyone else's account unless you use their login info to generate a new JWT unique their account. Your developer account API key & secret won't work on their account.

@apos37
Copy link
Collaborator

apos37 commented Apr 19, 2021

But why would it work on my other account that is separate from my developer account?

@oregondean
Copy link

Do you use the same ID and passcode on the separate account as your dev account? Or is your other account a free account? I don't think free accounts allow API access.

@apos37
Copy link
Collaborator

apos37 commented Apr 19, 2021

Different ID and passcodes. The other account is a Pro account. I will reach out to the clients and see if they are using free accounts. I'll see if I can figure it out. Thanks for the help!

@apos37
Copy link
Collaborator

apos37 commented Apr 19, 2021

Ah, I think I figured it out why it was working. Our zoom admin didn't tell me that the our other account is actually just a user from our developer account, so they are linked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants