Replies: 1 comment
-
This is because you haven't confirmed their phone and you have signup disabled. The first message sent out when using a magic link for a user who hasn't confirmed their phone number would be a signup one and since signup is disabled the message you are getting is correct. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When I create a user with supabase.auth.admin.createUser() without setting phone_confirm: true, attempting to log in with supabase.auth.signInWithOtp() fails with:
But if I create the user with phone_confirm: true, the login works as expected.
Steps to reproduce
Environment
• Auth: phone provider enabled
• Instance: phone signups enabled
config.toml
If a user is created via admin.createUser() they should already exist in the system.
So how can I mark the user's phone as confirmed after creation?
Beta Was this translation helpful? Give feedback.
All reactions