…but we’re still getting an SMS. If we hit Twilio’s Verify API directly via curl with the same credentials and parameters, the WhatsApp OTP comes through as expected:
Our Supabase Auth provider is configured with the same service SID, auth token, etc. It looks like the SDK isn’t forwarding the channel parameter to Twilio. Can you confirm whether there’s a regression here? This is blocking our WA flows, really appreciate the help!
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.