Sign-in error code invalid_client
What Synq's `invalid_client` sign-in error code means, why a sign-in came back to the app with it, and what to do.
Synq doesn't know the app's client_id at this brand, its secret didn't match, the app didn't authenticate the way it's set to, or the app is disabled. The token endpoint's error_description is the same whatever the cause, so it never tells whether a client_id exists.
What to do
The app's team checks its client_id, its secret and the issuer against the app's page in Synq's dashboard, and that the app is on. A web app sends its secret (client_secret_basic or client_secret_post); a single-page or native app sends only its client_id, with PKCE.
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_client).
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_client, and @synqauth/nextjs puts it in the page's address as synq_error=invalid_client 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 not_signed_in
What Synq's `not_signed_in` sign-in error code means, why a sign-in came back to the app with it, and what to do.
Sign-in error code unauthorized_client
What Synq's `unauthorized_client` sign-in error code means, why a sign-in came back to the app with it, and what to do.