Verify and log in through OTP - obsolete/incorrect information #14089
Labels
documentation
Improvements or additions to documentation
Comments
altryne
added a commit
to altryne/supabase
that referenced
this issue
May 2, 2023
… for emails `email` Fixes supabase#14089 supabase#14089 Specifies that `email` is the right type for OTP verification and adds `signup` and `magiclink` to be deprecated per supabase/auth#885 and supabase/auth-js#642
sh47dow
pushed a commit
to sh47dow/supabase
that referenced
this issue
May 29, 2023
… for emails `email` Fixes supabase#14089 supabase#14089 Specifies that `email` is the right type for OTP verification and adds `signup` and `magiclink` to be deprecated per supabase/auth#885 and supabase/auth-js#642
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Improve documentation
Verify and log in through OTP documentation
Link
https://supabase.com/docs/reference/javascript/auth-verifyotp
Describe the problem
The current page lists these types of verification
signup,magiclink,recovery,inviteoremail_changehowever, bothmagiclinkandsignuphave been deprecated in supabase/auth#885 in favor ofemailwhich is not listed there.emailworks for both newly created accounts and returning accounts who are logging in just now.Describe the improvement
emailshould replace both themagiclinkandsignuptypes as per the Pull RequestAdditional context
The above PR describes a fix for a problem with auth, where supabase would return a 401 for valid tokens every new user registration. IMO it's a huge deal, and have probably turned away so many folks that tried to use our product.
The text was updated successfully, but these errors were encountered: