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
On facebook login: AttributeError at /complete/facebook/ 'NoneType' object has no attribute 'expiration_datetime' #190
Comments
Its similar to #172 (but with facebook as the backend). I am using the latest available release (0.1.21).
|
Do you have a custom pipeline? |
My pipeline is
Which is standard + custom last step. I'll look into running the step with commenting out the last step of the pipeline and check if the error still exists. |
What does the last pipeline? |
I am getting the same issue too with
My pipeline is
|
I've introduced a change that might fix the issue, @mohitranka and @devangmundhra could you give it a try? |
Hi Matias, Somehow I don't see the error any more even before trying the fix (I Thanks. On Sat, Mar 15, 2014 at 10:39 AM, Matías Aguirre
|
Have the same problem on facebook, twitter and VK login(( |
@CrazyPilot, have you tried my fix at dec6d30 ? |
@omab, it doesn't help me. I also have such error with facebook and twitter. |
@sledopit, I've pushed another potential fix, could you give it a try? |
@omab. nope it also didn't fix it. some technical details:
it is almost the same as in OP trace. |
@sledopit, I'm not able to reproduce this issue, that's why it's so hard for me to fix it, could you trace back why |
@omab it's quite a challenge for me. I will try it, but I definitely need some time for investigations. |
@omab: FYI, I was also using a custom User Model when I was getting this On Sun, Mar 23, 2014 at 11:32 AM, sledopit notifications@github.com wrote:
|
@sledopit, @devangmundhra, I've tried a custom user model (it's in the example app) and it worked without issues, if any of you can build a simple app that reproduces the issue that I can clone and try here, please do. |
@omab, I tried to make a simple app to reproduce and there it works without this error. This is really strange as all things are absolutely the same (even User model app is just copied from my project ). I will try to find the diff between simple app and my. Hope I'll be lucky enough to catch the root. |
I encounter the same issue (vkontakte and odnoklassniki backends for me), as far as i can remember it has also appeared when i introduced a custom User model. I use the default pipeline. |
@htch, version? |
@omab, 0.1.23
|
I have seen a similar problem occurring with another open source project I was able to find the cause of the problem in that instance, which was One way to solve the problem there was to reload the I am not sure if this problem is related or not, though the symptoms are On Tue, Apr 1, 2014 at 10:43 AM, Pavel Kuznetsov
|
@htch, that version has my possible fixes to the issue, so they aren't working, are you able to create a simple small project that recreates the issue? |
@htch , check you database. when I recreated it from scratch everything became fine. I didn't figure out what was wrong in database, but the evil is in it. I still have both databases and with the old one I still can reproduce the bug. So it looks like some migration broke it at my side. |
I guess it does indeed have a lot to do with the state of the database.
Once I deleted the foreign key (obviously left from the time when I have switched from auth.User to my custom user model), the error disappeared. |
@htch +1 Same thing for me, the following database integrity error
fails silently because is catch by the line
|
Any resolution to this ? |
This problem is generated from the database. It happened to me when I deleted a user through PHPMyAdmin without deleting its relationships. When I deleted dropped the database and made a new migration, it was all gone. |
The text was updated successfully, but these errors were encountered: