-
Notifications
You must be signed in to change notification settings - Fork 299
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
[@clerk/nextjs]: Redirect to /sign-up when sign up with SSO and legal enabled #4586
Comments
Hey @dikaioai! I've tried to reproduce the issue but I could not, do you still face the issue? |
Hello Vangeli! I will provide a reproducible repository today. Thank you for reminding me about this. The issue occurs in the following scenario:
This scenario should be very rare in production. |
Hey! Thank you for sharing, I will take another look! |
Hey! I've tried to reproduce this one again but I'm still seeing the expected behaviour, have you seen the issue popup again? |
Hello, yes also one of our users had this issue using apple login and |
Has any fix been found for this issue? |
Preliminary Checks
I have reviewed the documentation: https://clerk.com/docs
I have searched for existing issues: https://github.com/clerk/javascript/issues
I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
Reproduction
https://github.com/dikaioai/clerk-nextjs-legal-oauth-error-reproduction
Publishable key
pk_test_aW5mb3JtZWQtY3JhYi0zMS5jbGVyay5hY2NvdW50cy5kZXYk
Description
Steps to reproduce:
Deps:
Dev deps:
Steps to Reproduce
Using the pre-build
SignUp
components from @clerk/nextjs package:Expected Behavior
After SSO authentication, users should be redirected to the
/sign-up/continue
page where they only need to accept the legal terms.Actual Behavior
Inconsistent behavior observed:
/sign-up
page with:Environment
The text was updated successfully, but these errors were encountered: