Sign-in error code unsupported_response_type
What Synq's `unsupported_response_type` sign-in error code means, why a sign-in came back to the app with it, and what to do.
The app asked for a response type Synq doesn't give: Synq answers with an authorization code only.
What to do
The app's team uses the authorization code flow with PKCE, as Synq's SDKs do.
What the person sees
This app’s sign-in isn’t set up right, so it can’t finish. It’s not something you did: tell the app’s team (code unsupported_response_type).
It's the app's own setup, which only its team can fix: trying again gets the same answer. A sign-in that doesn't finish comes back to the app with a code instead of a session. Synq's SDKs hand it over as the error's code, unsupported_response_type, and @synqauth/nextjs puts it in the page's address as synq_error=unsupported_response_type and says the words above (signInErrorMessage). Branch on the code, never on the words.
See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Sign-in error code invalid_redirect_uri
What Synq's `invalid_redirect_uri` sign-in error code means, why the sign-in stopped on Synq's error page with it, and what to do.
Sign-in error code discovery_failed
What Synq's `discovery_failed` sign-in error code means, why a sign-in came back to the app with it, and what to do.