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.
The app couldn't read the issuer's discovery document, or it named another issuer: the issuer the app is set to is wrong, or Synq couldn't be reached from the app's server.
What to do
The app's team checks the issuer the app is set to against the brand's, and that its server can reach it.
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 discovery_failed).
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, discovery_failed, and @synqauth/nextjs puts it in the page's address as synq_error=discovery_failed 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 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.
Sign-in error code method_not_offered
What Synq's `method_not_offered` sign-in error code means, why a sign-in came back to the app with it, and what to do.