Closed c-w closed 1 year ago
My fault on that! Sorry and thanks! ❤️
Is there an ETA on when this fix is going to be released?
I'm confused: the commit with the fix is tagged as 5.0.2. I am on 5.0.2, and I still get the issue.
Specifically, my versions for dj-rest-auth and django-allauth are:
# pyproject.toml
dj-rest-auth = {extras = ["with-social"], version = "^5.0.2"}
# poetry.lock
[[package]]
name = "dj-rest-auth"
version = "5.0.2"
description = "Authentication and Registration in Django Rest Framework"
optional = false
python-versions = ">=3.6"
files = [
{file = "dj-rest-auth-5.0.2.tar.gz", hash = "sha256:aad7d912476169e9991547bf98645344d3939be2d7052098048d819524c115d9"},
]
[package.dependencies]
Django = ">=3.2"
django-allauth = {version = ">=0.56.0,<0.58.0", optional = true, markers = "extra == \"with-social\""}
djangorestframework = ">=3.13.0"
[package.extras]
with-social = ["django-allauth (>=0.56.0,<0.58.0)"]
...
[[package]]
name = "django-allauth"
version = "0.57.0"
description = "Integrated set of Django applications addressing authentication, registration, account management as well as 3rd party (social) account authentication."
optional = false
python-versions = ">=3.7"
files = [
{file = "django-allauth-0.57.0.tar.gz", hash = "sha256:a095ef0db7de305d9175772c78e765ebd5fceb004ae61c1383d7fc1af0f7c5b1"},
]
My traceback is (as far as I can tell) exactly identical to the OP:
Upon further investigation, it looks like the commit was first released under 4.0.0, but this doesn't explain why the problem should still occur. Should this be a new issue?
I'm having the exact same error; seems like it's still not fixed or we're doing something wrong.
Django==3.2.18
dj-rest-auth==5.0.2
django-allauth==0.60.1
Have you fixed this or found a workaround @tadamcz ?
In https://github.com/iMerica/dj-rest-auth/pull/482 a regression was introduced for logging in with Google using the auth-code flow:
For the latest allauth, in the auth-code flow, the
token
variable already holds a dictionary with anid_token
field so it's unnecessary to wrap the response. This pull request fixes the regression.