Sign-in error code invalid_request
What Synq's `invalid_request` sign-in error code means, why a sign-in came back to the app with it, and what to do.
The app's sign-in request was malformed: a parameter missing or not valid, such as PKCE.
What to do
The app's team updates its Synq SDK, or checks its request against the protocol guide.
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 invalid_request).
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, invalid_request, and @synqauth/nextjs puts it in the page's address as synq_error=invalid_request 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.