AI & Agent Dev Bug Sandbox Back to Radar

Verification Code Not Delivered Due To Missing Or Incorrect Auth Provider Configuration

Users are not receiving verification codes during authentication because the Supabase project lacks proper SMTP/SMS configuration or relevant settings are disabled.

mediumConfidence 65%Supabase

Origin Analysis

The Supabase Auth service is not sending verification codes because the project's email/SMS provider settings are not configured correctly, or the corresponding authentication settings (like 'Enable email confirmations') are turned off. This can also be caused by rate limiting or provider outage, but the most common cause is misconfiguration.

1. Navigate to Supabase project dashboard. 2. Go to Authentication > Providers. 3. Check Email/SMS provider configuration. 4. Confirm that SMTP settings are filled correctly and 'Enable email confirmations' is toggled on. 5. Attempt to sign in with email/phone and observe no code is received.

Fixing Code Block

# Enable email confirmations in Supabase Dashboard
# Or set via CLI:
supabase secrets set SMTP_HOST=smtp.sendgrid.net
supabase secrets set SMTP_PORT=587
supabase secrets set SMTP_USER=apikey
supabase secrets set SMTP_PASS=your_sendgrid_api_key
supabase secrets set SMTP_ADMIN_EMAIL=admin@example.com
supabase secrets set SMTP_SENDER_NAME="Your App"

The provided commands set the SMTP environment variables required by Supabase Auth to send emails. After setting these, restart the Auth service (or in managed Supabase, it applies automatically) and test again. Ensure the 'Enable email confirmations' option is enabled in the dashboard under Authentication > Providers > Email.

Edge Case Audit

Changing SMTP settings can affect all outgoing emails, including password resets and invitations. Ensure the SMTP provider is reliable and credentials are correct to avoid service disruption. Also, monitor rate limits to avoid temporary blocks. Rollback by reverting to previous configuration values if issues occur.