Auth Flow Diagnostic Tracer

Trace signup → email verification → callback → session creation

📦 PKCE State & Storage

localStorage:
(empty - no PKCE verifier present)
sessionStorage:
(empty - no PKCE verifier present)

🔍 Complete Diagnostic Trace

No trace data yet. Click "Start Signup & Trace Flow" to begin.

📋 What This Diagnostic Shows:

  • Signup Response: User creation and email confirmation status from Supabase Auth
  • Email Provider Detection: Whether Supabase native mailer or edge function is used
  • Email Delivery Status: Inference from user object (if email_confirmed_at is null, email was queued)
  • PKCE State: Whether a code_verifier exists in browser storage
  • Session State: Whether authentication session was created
  • Redirect Flow: Expected URL pattern from Supabase email template
  • Callback Parameters: What code/error parameters arrive at /auth/callback
⚠️ Limitations of this diagnostic:
  • Cannot directly access Supabase Auth email logs (requires Supabase dashboard access)
  • Cannot see email provider SMTP responses without server-side logging
  • Cannot confirm actual email delivery to inbox (only infer from user object)
  • Email delivery status must be verified manually by checking inbox