SynqDocs
Errors

Sign-in error code invalid_response

What Synq's `invalid_response` sign-in error code means, why a sign-in came back to the app with it, and what to do.

Synq's answer failed one of the app's checks: the ID token, its nonce, or a subject that changed. Often a clock far off on the app's server, or two apps sharing one callback.

What to do

The app's team checks its server's clock and that each app has its own callback, then tries again.

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_response).

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_response, and @synqauth/nextjs puts it in the page's address as synq_error=invalid_response 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.

On this page