New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling Post-Signup Email Verification without Blocking User Sign-In on Supabase (Resend) #991
Comments
I believe you have set If you want to implement "mail verification post sign-up" I would recommend using a custom Edit: For reference, this is how Supabase's |
+1 For this feature. According to docs this have been possible but is deprecated? But I couldn't find more when, why and in what PR. There is old issue for this without update supabase/auth#453 |
I had idea for hacky workaround which should be possible. But I didn't properly test this! See bottom
I didn't test this properly because it would require me to set webhooks and triggers manully on production. Because on production and local development webhook url is different.
That causes issues with migration files. As it is not possible to reference right url in the migration files. Here are two more issues related to this that I found: |
I am also interested in a way to enable post-signup verification. While a custom backend (using A few observations:
With this, I think it would be great to allow devs to configure |
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: