Using Bolt.new to build my webapp. Claimed supabase database.
Supabase: Twitter provider is toggled ON.
Twitter Dev Portal: App is set to "Web App," User Authentication is ON, and "Request email from users" is enabled.
Callback URL: Copied directly from Supabase into Twitter Dev settings.
Env Vars: Cannot confirm that the SUPABASE_URL and ANON_KEY match the project where the provider is enabled because Bolt automatically created the new supabase org when I clicked it.
The Issue: Despite everything being "ON," the API response still claims the provider is disabled. Is there a known delay in provider propagation, or a specific "Site URL" wildcard setting in Supabase Auth that I might be missing for Bolt.new preview URLs?
Appreciate any insights!