Authentication Failed (with valid credentials, CLI is working fine)

Description

I can use the app for about a month or so, then suddenly (seemingly randomly) it will refuse to authenticate, even if i provide valid credentials. I can still use git on the command line with no issues

Usually I solve this by deleting all of my ssh keys, both locally and on github, regenerating and re-adding them, this is a annoying but necessary. If there was a more ‘proper’ way of solving this, i would really like to hear it.

For now i can make do with the command line, but this was a really useful tool and would love to see it working again.

Version

1.1.1

• GitHub Desktop:

• Operating system: OSX 10.12.6

Steps to Reproduce

Use github desktop for a few months

Expected Behavior

make commits, push, pull etc, normal git stuff

Actual Behavior

Log in box pops up and refuses to accept any credentials i give it

Logs

~/Library/Application Support/GitHub Desktop/logs/*.desktop.production.log does not exist have done a full search for anything containing .desktop.production.log but no luck

[guardrex]

I’ve chatted with GH Support. The problem in my case seems to be that with 2FA activated my GH password won’t work in either in the login panel or in the CLI … a personal access token has to be created and used …

https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/

Further, the CLI won’t remember the token session-to-session, so I need to follow the instructions to cache a token (which I haven’t done yet, but will to later today) …

https://help.github.com/articles/caching-your-github-password-in-git/

NOTE TO OWNERS Someone really dropped the ball here on surfacing migration info during the GH Desktop installation process. IIRC, I didn’t need to go thru these steps with the prior GH Desktop, perhaps because I activated 2FA at some point later. However, these probs should’ve been foreseen, and you should’ve taken steps to surface these migration details during the install process using screens that the installer shows. Throwing auth error messages at the user when they’re providing correct login credentials is a horrible user experience. It’s a waste of my time and the time of the GH Support cats.

[guardrex]

Just wanted to add … same here. I was using the old GH Desktop for several years without problem. It seems to have reached a point where it forced me to upgrade.

Current behavior is that GH Desktop (the app) authenticates and works as expected. The CLI tho doesn’t … It asks me for credentials in a pop-up panel first … and then flips over to the command line asking for credentials. It won’t authenticate. For something like a force push, I can’t use the UI, so I’m pretty much broken at the moment.

I’ve put in a support request with GH to see if they can help.