Hey @pb_zoom, @josharcher,
Can you please share a screenshot of the error?
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.
If possible please limit to using a single value in the state parameter.
Make use of the base64UrlEncode function to encode the state parameter
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.