Recent Commit Broke Signup/Login Flow When Using verifyOTP
Another user posted about this issue here help-and-questionsGetting an error of: "User has more than one identity on signup" and I commented on that issue.
I'd like to escalate this though since the issue is causing our users a lot of annoyance.
Here's a link to the github issue: https://github.com/supabase/auth/issues/1899
Basically, a recent commit to the Supabase Auth Go Service now expects a user to only have a single identity before confirmation.
However, our use case was to previously do the following:
This use-case worked fine up until this commit seems to have introduced the problem:
https://github.com/supabase/auth/commit/483463e49eec7b2974cca05eadca6b933b2145b5#diff-e47b259bf17912f7ca1f5163ccbfb8a8c23da6c399412ce5aef78b8b684df5e5R330
We now receive
I'd like to escalate this though since the issue is causing our users a lot of annoyance.
Here's a link to the github issue: https://github.com/supabase/auth/issues/1899
Basically, a recent commit to the Supabase Auth Go Service now expects a user to only have a single identity before confirmation.
However, our use case was to previously do the following:
- Create a user using auth.createUser and pass in both email and phone params.
- Call auth.signInWithOtp with an email address or phone
- Call auth.verifyOtp with email and `type: 'email`` or with phone and type: 'phone'
This use-case worked fine up until this commit seems to have introduced the problem:
https://github.com/supabase/auth/commit/483463e49eec7b2974cca05eadca6b933b2145b5#diff-e47b259bf17912f7ca1f5163ccbfb8a8c23da6c399412ce5aef78b8b684df5e5R330
We now receive
User has more than one identity on signup when calling verifyOtp and have a bunch of users that are unable to login with their email addresses.GitHub
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 An auth bug of "User has mo...
