-
Notifications
You must be signed in to change notification settings - Fork 15
Reverse for 'socialaccount_signup' not found. 'socialaccount_signup' is not a valid view function or pattern name. #7
Comments
Hi, need a bit more information. Once the |
One other thing, your issue sounded familiar to something I had faced in a different project. Here is the corresponding issue that explains the situation (the solution is the same as the StackOverflow post but it's only partial). Can you confirm that the situation (not the solution) matches with yours? |
Hi @mahieyin-rahmun, I believe it is the same situation from the other project. How do you suggest I fix this? Would it be an issue with next-auth on the front end or allauth on the backend? |
A thing to note is that: I came to the full solution using Chrome Dev Tool's network tab. When this "account clash" happens, DRF actually sends back a response but we're too focused on the error in the DRF server terminal. Here's the code snippet from my other project, which should be put in
See if it works. You should not be able to sign in when the clash happens, but your frontend will be more descriptive about it. Happy holidays. |
Thank you so much! 🙏 |
I'm getting this error where I can't sign up new users using Google Sign in. (existing users can sign in).
I found this solution online: https://stackoverflow.com/a/41241934, while it did make this particular error message go away, I was still not able to login with google.
I've added this to my
urlpatterns
according to the tutorial:path("api/auth/", include("dj_rest_auth.urls")),
, but there was no mention of adding asocialaccount_signup
path.Any help would be greatly appreciated and thank you for this tutorial!
Happy holidays!
The text was updated successfully, but these errors were encountered: