© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•13mo ago•
2 replies
David HHT

Phone provider with SMS sending hook always raises errors

I implemented the Send SMS Hook for the regional sms providers.

In our Fullter app, the following steps to sign in with OTP and resend OTP always raise errors:

1. The first time, call
signInWithOtp
signInWithOtp
to request an SMS OTP, it works successfully.
2. Verify OTP with
verifyOTP(phone, token, type: OtpType.sms);
verifyOTP(phone, token, type: OtpType.sms);
always return an error
message: Token has expired or is invalid, statusCode: 403, errorCode: otp_expired)
message: Token has expired or is invalid, statusCode: 403, errorCode: otp_expired)
.
3. Try to resend OTP with
signInWithOtp
signInWithOtp
again.
4. Repeating the verification in step 2 results in the same error.

Can you help to solve this issue? Or is this the bug of supabase auth?
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

SMS-Hook with Twilio Verify
SupabaseSSupabase / help-and-questions
4mo ago
Failed to get SMS provider
SupabaseSSupabase / help-and-questions
6mo ago
Custom SMS Provider for AUTH
SupabaseSSupabase / help-and-questions
4y ago
I want to use Custom sms provider when doing registration with phone verifying otp
SupabaseSSupabase / help-and-questions
8mo ago