-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Social Authentication Error when setting SOCIALACCOUNT_STORE_TOKENS #3599
Comments
miqsoft
added a commit
to miqsoft/django-allauth
that referenced
this issue
Jan 18, 2024
set token.app to None if app is not saved in database but only in settings (social authentication)
miqsoft
added a commit
to miqsoft/django-allauth
that referenced
this issue
Jan 18, 2024
set token.app to None if app is not saved in database but only in settings (social authentication)
miqsoft
added a commit
to miqsoft/django-allauth
that referenced
this issue
Jan 18, 2024
fix issue pennersr#3599 by checking before a token update if app instance is saved to database. If not set app instance to None.
miqsoft
added a commit
to miqsoft/django-allauth
that referenced
this issue
Jan 18, 2024
fix issue pennersr#3599 by checking before a token update if app instance is saved to database. If not set app instance to None.
Closed
Fixed via 5f71a37 |
This does fix the error. But I'm a little worried that we lose the information for which app the socialtoken is. Could we store it as Char (in a CharField)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello guys,
When setting SOCIALACCOUNT_STORE_TOKENS I get error
save() prohibited to prevent data loss due to unsaved related object 'app'
.I assume it occurs since the SocialApp instance is not saved to database and instead created from data from the settings. However I do not know how resolve it properly.
Versions:
Django==4.2
django-allauth==0.60.1
Stacktrace:
Configuration:
The text was updated successfully, but these errors were encountered: