supabase: sms Provider twilio-verify could not be found
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When trying to use the new Twilio Verify feature in Supabase the following error message gets returned when attempting to sign in with OTP: error: AuthException(message: Error sending sms: sms Provider twilio-verify could not be found, statusCode: 400)
To Reproduce
Try to sign in in Flutter with client.auth.signInWithOtp(phone: phoneNumber)
Expected behavior
The method succeeds and OTP SMS is sent.
Screenshots
System information
Additional context
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 17 (5 by maintainers)
Apparently this is not yet in the CLI:
https://discord.com/channels/839993398554656828/1139583687533547550/1140352446036717579
Any ETA on when this will be shipped? At least to the beta?
Hey all,
Apologies for the late update - I temporarily removed the provider as I later realized the Auth service has yet to be updated with the relevant version to support the change (thus the backend error).
If you’d like, feel free to reach out to support and I can update your project to provide early access until it’s rolled out across all projects. The integration between the dashboard and corresponding service should have been better tested and that is fault on my part.
Please rest assured that we have done thoroughly tested the backend and that it is functioning as expected. I’m really sorry for the inconvenience caused - the Auth service should be updated this week and it should be reinstated early next week.
I’m going to pull the docs for now as well so as to avoid further confusion
Hey @Kypsis,
Thanks for flagging this, the frontend should be sending over twilio_verify instead of twilio-verify. Putting in a fix now - apologies for the inconvenience caused