It’s a 2015 MacBook pro running chrome Version 83.0.4103.116.
First error
Access to XMLHttpRequest at '[https://marketplace.zoom.us/api/v1/apps/Scjgw1tqQ0STWg5L2Pv6Rw/@grant?zpk=eyJhbGciOiJIUzUxMiIsInYiOiIyLjAiLCJraWQiOiIxMGY3YzgyYy04NjU2LTQ5MDAtYWJlZC0yOTE1YWRlNjVkMjYifQ.eyJhdWQiOiJodHRwczovL2FwcC56b29tLnVzIiwibmJmIjoxNTkzNTU4MjI5LCJhY2NvdW50X2lkIjoiaTRTcXRWVFBUMVd6ZFduV2dvV1BsZyIsImF1dGhfaWQiOiJNS2d6NGZBR2hBR1V0L05UL05HdXY1ay9vMjE4QzU5eks0SEhBU3RrVzRvPSIsInVzZXJfaWQiOiJDdXZpekQ3WFI4NjlLWkFobnRqbHJRIiwidXNlcl9uYW1lIjoiSm9zaCBBcmNoZXIiLCJpc3MiOiJodHRwczovL3dlYi56b29tLnVzIiwiZXhwIjoxNTkzNTY1NDI5LCJ0eXBlIjoxLCJpYXQiOjE1OTM1NTgyMjksImp0aSI6ImRjZWJjNTM1LWE2ZjQtNGVhMi1iZDcyLWE1MzY4OGVmNzY1MSJ9.fvEkZAGdNOlShXD621MFO1p4Q67Xl6iiuRB3QpQasjFUC5ZWUWdgyRuOaZjQDiUBddMkci5TvXsbl7Rn8Q3FcQ&scopes=meeting:write,recording:write,user:read&state={%22userId%22:%22l2hWkuaSo4csUnVffJjO%22,%22clientRedirect%22:%22https://pro.sutra.fit/dashboard/business-settings%22}](https://marketplace.zoom.us/api/v1/apps/Scjgw1tqQ0STWg5L2Pv6Rw/@grant?zpk=eyJhbGciOiJIUzUxMiIsInYiOiIyLjAiLCJraWQiOiIxMGY3YzgyYy04NjU2LTQ5MDAtYWJlZC0yOTE1YWRlNjVkMjYifQ.eyJhdWQiOiJodHRwczovL2FwcC56b29tLnVzIiwibmJmIjoxNTkzNTU4MjI5LCJhY2NvdW50X2lkIjoiaTRTcXRWVFBUMVd6ZFduV2dvV1BsZyIsImF1dGhfaWQiOiJNS2d6NGZBR2hBR1V0L05UL05HdXY1ay9vMjE4QzU5eks0SEhBU3RrVzRvPSIsInVzZXJfaWQiOiJDdXZpekQ3WFI4NjlLWkFobnRqbHJRIiwidXNlcl9uYW1lIjoiSm9zaCBBcmNoZXIiLCJpc3MiOiJodHRwczovL3dlYi56b29tLnVzIiwiZXhwIjoxNTkzNTY1NDI5LCJ0eXBlIjoxLCJpYXQiOjE1OTM1NTgyMjksImp0aSI6ImRjZWJjNTM1LWE2ZjQtNGVhMi1iZDcyLWE1MzY4OGVmNzY1MSJ9.fvEkZAGdNOlShXD621MFO1p4Q67Xl6iiuRB3QpQasjFUC5ZWUWdgyRuOaZjQDiUBddMkci5TvXsbl7Rn8Q3FcQ&scopes=meeting:write,recording:write,user:read&state={%22userId%22:%22l2hWkuaSo4csUnVffJjO%22,%22clientRedirect%22:%22https://pro.sutra.fit/dashboard/business-settings%22})' from origin '[https://zoom.us](https://zoom.us)' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Second error
csrf_js:96 GET [https://marketplace.zoom.us/api/v1/apps/Scjgw1tqQ0STWg5L2Pv6Rw/@grant?zpk=eyJhbGciOiJIUzUxMiIsInYiOiIyLjAiLCJraWQiOiIxMGY3YzgyYy04NjU2LTQ5MDAtYWJlZC0yOTE1YWRlNjVkMjYifQ.eyJhdWQiOiJodHRwczovL2FwcC56b29tLnVzIiwibmJmIjoxNTkzNTU4MjI5LCJhY2NvdW50X2lkIjoiaTRTcXRWVFBUMVd6ZFduV2dvV1BsZyIsImF1dGhfaWQiOiJNS2d6NGZBR2hBR1V0L05UL05HdXY1ay9vMjE4QzU5eks0SEhBU3RrVzRvPSIsInVzZXJfaWQiOiJDdXZpekQ3WFI4NjlLWkFobnRqbHJRIiwidXNlcl9uYW1lIjoiSm9zaCBBcmNoZXIiLCJpc3MiOiJodHRwczovL3dlYi56b29tLnVzIiwiZXhwIjoxNTkzNTY1NDI5LCJ0eXBlIjoxLCJpYXQiOjE1OTM1NTgyMjksImp0aSI6ImRjZWJjNTM1LWE2ZjQtNGVhMi1iZDcyLWE1MzY4OGVmNzY1MSJ9.fvEkZAGdNOlShXD621MFO1p4Q67Xl6iiuRB3QpQasjFUC5ZWUWdgyRuOaZjQDiUBddMkci5TvXsbl7Rn8Q3FcQ&scopes=meeting:write,recording:write,user:read&state={%22userId%22:%22l2hWkuaSo4csUnVffJjO%22,%22clientRedirect%22:%22https://pro.sutra.fit/dashboard/business-settings%22}](https://marketplace.zoom.us/api/v1/apps/Scjgw1tqQ0STWg5L2Pv6Rw/@grant?zpk=eyJhbGciOiJIUzUxMiIsInYiOiIyLjAiLCJraWQiOiIxMGY3YzgyYy04NjU2LTQ5MDAtYWJlZC0yOTE1YWRlNjVkMjYifQ.eyJhdWQiOiJodHRwczovL2FwcC56b29tLnVzIiwibmJmIjoxNTkzNTU4MjI5LCJhY2NvdW50X2lkIjoiaTRTcXRWVFBUMVd6ZFduV2dvV1BsZyIsImF1dGhfaWQiOiJNS2d6NGZBR2hBR1V0L05UL05HdXY1ay9vMjE4QzU5eks0SEhBU3RrVzRvPSIsInVzZXJfaWQiOiJDdXZpekQ3WFI4NjlLWkFobnRqbHJRIiwidXNlcl9uYW1lIjoiSm9zaCBBcmNoZXIiLCJpc3MiOiJodHRwczovL3dlYi56b29tLnVzIiwiZXhwIjoxNTkzNTY1NDI5LCJ0eXBlIjoxLCJpYXQiOjE1OTM1NTgyMjksImp0aSI6ImRjZWJjNTM1LWE2ZjQtNGVhMi1iZDcyLWE1MzY4OGVmNzY1MSJ9.fvEkZAGdNOlShXD621MFO1p4Q67Xl6iiuRB3QpQasjFUC5ZWUWdgyRuOaZjQDiUBddMkci5TvXsbl7Rn8Q3FcQ&scopes=meeting:write,recording:write,user:read&state={%22userId%22:%22l2hWkuaSo4csUnVffJjO%22,%22clientRedirect%22:%22https://pro.sutra.fit/dashboard/business-settings%22}) net::ERR_FAILED
Couple questions:
is this a CORS issue on Zoom’s end or my end?
does this have something to do with passing state in the Zoom oauth request? I’m trying to pass an URI encoded json object with some user state.
Our engineering team is aware of the issue and investigating this. While the team is yet to confirm the exact cause of error, upon initial review, they suspect the issue lies with this specific use of the state parameter. In the meantime they have advised that you revise the OAuth URL to not use a state parameter and it should resolve the authorization error.
For a quick resolution, if you still plan to use the state parameter you can try either of these options.
The engineering team is investigating this at priority and we will keep you updated on the status. Let me know if neither of these help resolve the error you are encountering.