Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
I keep getting "You are not logged into Github.." Messages on Sync.. every day / every machine #202
So this seems a bit weird - after updating to the latest version of your VS Github extension it appears I am getting logged out.. every day.. on two different machines.
I have logged in again and again on both machines and these messages appear to come back every day..? I have 2-factor authentication enabled and therefore always hit that other bug where to 2fa dialog never closes for which I keep waiting a little while giving it some time and it appears to work by then (read: I seem to be logged in).. but having to do that over and over again every day is .. a bit.. annoying.
Is there any log / data the extension writes why this is happening & what might help you?
@jbattermann That's good, that means you're logged in and git operations on github.com repositories will work inside VisualStudio (and anything else that knows to use your stored credentials)
The persistence looks wrong though! That's why you keep getting logged off every day, they're cleared when you log off. That's incredibly helpful, thank you! I'll get that fixed right away.
added a commit
Jan 15, 2016
@jbattermann I just published a beta with a fix for this. It's still undergoing testing, but if you want to try it out, you can download it from the releases page, or configure a gallery in Visual Studio to get beta versions.
To configure the beta gallery, go to
Hrrrmmmm.. quick update here - I had to log in again today :-/ (on the machine I rebooted a few times yesterday and where it seemed to work perfectly fine) - the extension.log says the following:
I logged in again (2fa worked as expected again - window closing etc), I shutdown VS, and then rebooted the machine.. and I am still logged in.
Not sure what happened inbetween yesterday and tonight that cause the logout / error(s) above, but maybe you see something..
Hrm - today it worked and I can't reproduce the problem from yesterday.. I'll just keep an eye on it and if it happens again, I'll just re-open this issue. Persistence is set to Local Computer in Windows' Credentials Manager - at least now it is.. I hadn't checked yesterday - however it says 'Modified 20.01.2016'.. so yesterday.
Ah well - I'll let you know if it re-occurs. Thanks a lot either way :)