-
Notifications
You must be signed in to change notification settings - Fork 309
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
SignUpButton fails to authenticate user if Facebook account was previously linked #4803
Comments
Hello 👋 We currently close issues after 40 days of inactivity. It's been 30 days since the last update here. If we missed this issue, please reply here. Otherwise, we'll close this issue in 10 days. As a friendly reminder: The best way to see an issue fixed is to open a pull request. If you're not sure how to do that, please check out our contributing guide. Thanks for being a part of the Clerk community! 🙏 |
This is still an issue. |
Hey @gabrielmaldi this should have been resolved in #4961 |
Hi, @alexcarpenter. Just tested this and it didn't work for me. From Facebook I get redirected to |
@gabrielmaldi can you provide a minimal repo of your setup that includes the issue for us to help debug. |
@gabrielmaldi Also would you mind confirming if this is only with Facebook login? Does the issue happen if you use Google or Microsoft? |
@dstaley, yes, just tested with Google and got the same result: I get redirected to If I use @alexcarpenter, I won't have enough time to produce a minimal repo for a while, sorry. Thanks! |
@gabrielmaldi ah ok, I am assuming you don't have a mounted |
@alexcarpenter, yes, we have both a login and a signup button in the header: ![]() You can repro this issue in: https://beta.ad-in.me Thanks! |
@gabrielmaldi thanks for the link. The |
@alexcarpenter, adding a |
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://app.replay.io/recording/localhost3000--a6a7a2fd-696d-43ef-b216-ce4c9f3114df?commentId=&focusWindow=eyJiZWdpbiI6eyJwb2ludCI6IjAiLCJ0aW1lIjowfSwiZW5kIjp7InBvaW50IjoiNTg0MTMzMzk2NjUwOTU4NTM2MjQwNzE2NDEzNTYwNDIyNCIsInRpbWUiOjM2OTB9fQ%253D%253D&point=324518553658633099732480646185098&primaryPanel=tour&secondaryPanel=console&time=133&viewMode=non-dev
Publishable key
pk_test_Z2xvd2luZy1iYXQtOTguY2xlcmsuYWNjb3VudHMuZGV2JA
Description
Steps to reproduce:
<SignUpButton mode="modal">
Expected behavior:
The user is taken back to the site and is now logged-in.
Actual behavior:
The user is taken back to the site but is not logged-in.
The URL is
http://localhost:3000/#/sso-callback
and these are the requests:Everything works fine if I use
<SignInButton>
instead, or if I selectAlready have an account? [Sign in]
in the sign-up modal (before selecting Facebook):In those cases, these are the requests:
The one I highlighted seems to be the one making auth work. And the final URL is
http://localhost:3000/
(no/#/sso-callback
).I'm not using either of:
NEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL
,NEXT_PUBLIC_CLERK_AFTER_SIGN_UP_URL
,forceRedirectUrl
,signInForceRedirectUrl
,signUpForceRedirectUrl
.My reasoning is that since if I first select
Already have an account? [Sign in]
, everything works, then this is probably a bug inSignUpButton
.Thanks
Environment
The text was updated successfully, but these errors were encountered: