same issue for me - the same code works with one of my clients personal meeting id’s but not another client’s, so it’s not consistent? DM me if you want the meeting id’s of the one that works and one that doesnt
Oh i should probably specify that this is an issue we’re seeing with a webinar type. Same code that worked on 1.7.2 before last Friday. All keys and signatures are the same for 1.7.4, only CDN paths have been updated. There was no other “new” instructions given in https://github.com/zoom/sample-app-web
This still doesn’t work, even with your sample app project, added my zoom api keys, trying to join a scheduled meeting and we can’t get past this “The service is temporarily” message.
If you can DM me the meeting IDs that are working and not working also your developer emails from marketplace so that we can continue investigating this issue.
I am just getting started w/ this SDK by trying to run the sample app and getting the same message. Just so I understand, for those that have been here before, should I expect a resolution to be posted here?
Update, now I get an invalid password message. This is new.
I traced this new behavior down to passwords with special characters in it like @, something that will be escaped. I made it a simpler password and was able to join with the sample app.
My guess is the code changes on /info endpoint don’t html-unescape the password correctly @Michael_Purnell
Does anyone know what the sample app is actually supposed to do? Behavior has changed for me. I am no getting the a message saying the request timed out, but the actual httprequest response indicates that the signature is invalid.
Glad that it’s working. We are working on new versions of the WebSDK to improve the user experience. In the meantime let us know if you need anything else.