Auth Troubleshooting
What This Is
A symptom-driven debugging guide for Sign in with Lovelace.
Who This Is For
Developers investigating auth integration failures.
What You Will Finish With
- Faster diagnosis of common failures.
- Exact, actionable fixes.
Symptom: Sign-In Fails in Production
Diagnosis: Missing NEXT_PUBLIC_LOVELACE_OAUTH_CLIENT_ID.
Fix: Set the variable to a registered client ID.
Symptom: Verify Route Returns Unauthorized
Diagnosis: Audience or issuer mismatch.
Fix: Ensure verify route audience equals registered client ID and issuer matches Accounts issuer.
Symptom: Browser Always Redirects
Diagnosis: FedCM unsupported or disabled by browser policy.
Fix: Expected fallback behavior. Keep redirect flow configured.
Symptom: Session Not Established After Verification
Diagnosis: App route verified token but did not persist session.
Fix: Ensure successful verification path sets app session cookie/state.