AI & Agent Dev Bug Sandbox Back to Radar

Phone Provider Enabled In Dashboard But Runtime Still Reports Phone=False And Returns Phone_provider_disabled

In a managed Supabase Cloud project, the Phone Provider is toggled ON and SMS Provider set to Twilio Verify in the Dashboard, but the Auth runtime settings endpoint still reports phone=false and sms_provider='twilio'. Consequently, POST /auth/v1/otp fails with HTTP 400 and error_code phone_provider_disabled. The user has verified Twilio credentials work directly and there are no environment variable overrides or application-level configurations. This indicates a configuration propagation bug between the Dashboard and the Auth runtime.

highConfidence 75%Supabase Auth (GoTrue)

Origin Analysis

The Auth runtime configuration is not being updated when the Phone Provider is enabled via the Dashboard. The runtime still holds the old configuration (phone=false, sms_provider='twilio'), even though the Dashboard UI reflects the intended changes. This could be caused by a failed or silently ignored configuration update, a stale cache in the managed Auth service, or a mismatch between the Dashboard's internal representation and the runtime's expected configuration schema (e.g., Twilio Verify may require sms_provider='twilio_verify' instead of 'twilio', and the phone flag may be derived from the provider setting).

1. On a managed Supabase Cloud project, navigate to Authentication > Providers > Phone. 2. Toggle Phone Provider ON and set SMS Provider to Twilio Verify. 3. Save the configuration. 4. Call GET /auth/v1/settings and observe phone=false and sms_provider='twilio'. 5. Call POST /auth/v1/otp with a valid phone number; receive HTTP 400 with error_code phone_provider_disabled. 6. Toggle Phone Provider OFF then ON again; the runtime configuration remains unchanged.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Applying this fix without proper testing could inadvertently enable phone authentication for projects that rely on email-only signups. The mapping change from 'twilio' to 'twilio_verify' should be backward-compatible and only applied when the Dashboard explicitly selects Twilio Verify. The fix should be rolled out gradually with monitoring for unexpected configuration changes or increased SMS costs. A rollback plan should include restoring the original config loader logic and invalidating any caches to revert to previous behavior.