Changing OAuth scopes results in 500 server error
Closed this issue · 1 comments
jchristgit commented
If the user messes with the OAuth scopes for some reason, the socialaccount save signal will incorrectly assume that various attributes are set. If we don't have the required data in the response, we should just proceed to treat the user like a guest and possibly show an error message informing about the process not finishing properly.
Thanks to Natan for reporting this.
jchristgit commented
should be fixed in 8873ab3