Invalid or expired sign-in session — try again
Social login callback failed because the OAuth state cookie/payload was missing, expired, or did not match the provider (oauth_invalid_session). Product: try again.
Why this happens
decodeOAuthState failed or state.provider ≠ the callback provider. Typical causes: long delay before returning from Google/etc., cookies blocked, opened callback in a different browser, or stale tab. Distinct from provider token exchange failures (Could not complete sign-in with the provider).
Diagnose and fix
1. Start sign-in again from the login page (do not reuse an old callback URL).
2. Allow cookies; use the same browser/device for the whole flow.
3. Confirm OAuth redirect URI and site URL match the live HTTPS origin.
4. Admin: provider enabled under Social login with valid client credentials.