You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to improve the user experience in my application by allowing users to sign in immediately after registration, even before verifying their email. The default behavior in Supabase requires users to verify their email before they can sign in, which I believe creates a poor user experience. I want to give users the ability to verify their email after they have signed in by sending them a verification link or preferably a code to verify their email. However, I'm facing an issue where I cannot send a verification link to users using the Supabase Auth resend method for this purpose.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Initialize Supabase auth with a user's email and password.
Try to send the user a verification email after sign-up (not blocking sign-in) using the resend method as follows:
I expect to be able to send users a verification email (or ideally a verification code) after they have signed up and signed in, without blocking their initial sign-in due to unverified email. This approach aims to enhance the user experience by not forcing email verification before the user can explore the application.
Additional context
This issue is critical for user onboarding and directly impacts the user experience in our application. If there's an alternative approach to achieve this behavior or if someone has solved a similar issue, insights would be greatly appreciated. Ideally, I would like to send a verification code that users can enter to verify their email, but currently, the primary issue is the inability to resend the verification link after the user signs in.
The text was updated successfully, but these errors were encountered:
As @GaryAustin1 mentioned, the anonymouse authenticated user is an upcoming feature that could solve this. Unfortunately, other methods would require custom implementing (using Auth Hooks) as a user is only verified once the email is.
There is an issue with your approach in that users can then "game" the system by providing a fake email for the initial access if they realise that functionality exists.
I will close this for now as the upcoming feature could allow an implementation of this.
Bug report
Describe the bug
I am trying to improve the user experience in my application by allowing users to sign in immediately after registration, even before verifying their email. The default behavior in Supabase requires users to verify their email before they can sign in, which I believe creates a poor user experience. I want to give users the ability to verify their email after they have signed in by sending them a verification link or preferably a code to verify their email. However, I'm facing an issue where I cannot send a verification link to users using the Supabase Auth
resend
method for this purpose.To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
resend
method as follows:Expected behavior
I expect to be able to send users a verification email (or ideally a verification code) after they have signed up and signed in, without blocking their initial sign-in due to unverified email. This approach aims to enhance the user experience by not forcing email verification before the user can explore the application.
Additional context
This issue is critical for user onboarding and directly impacts the user experience in our application. If there's an alternative approach to achieve this behavior or if someone has solved a similar issue, insights would be greatly appreciated. Ideally, I would like to send a verification code that users can enter to verify their email, but currently, the primary issue is the inability to resend the verification link after the user signs in.
The text was updated successfully, but these errors were encountered: