Github Desktop no longer recognizes online repo?

I made some changes locally, and Github Desktop says “No local changes.  Push 1 commit to the remote.”  But when I click on “Push Origin”, it acts like I have never done that before.  It brings up the “Publish Repository” dialog.  And if I click “Publish” I get an error and it says the name already exists on this account.  Duh! That’s what I want it to connect to!  What am I doing wrong???

Hi and welcome @bsabiston ,

I get that is very frustrating! Let’s see if we can get that resolved.

If you are familiar with the command line, would you mind running  git remote -v  for us while inside of the repository?

If not, that is not a big problem either! Can you just try to freshly clone the repo from your account and see if the problems persist?

Thanks for the reply. I’m at work right now, but I’ll try it when I get home.

I don’t think I can freshly clone from my account because then I would lose my local changes, wouldn’t I?

No hurries, do post back when you’re home!

What I meant was just freshly cloning it into a different directory for testing purposes. That shouldn’t overwrite your changes.

OK when I run ‘git remote -v’, it shows this:

origin (fetch)

origin (push)

I also cloned the repo into a new test directory, but now what?  Do I have to copy over the changed files from the broken one or is there a way to get it working?

From my end the things seem to be set up correctly then.

I’d think that copying over the changes to a freshly cloned repo is the best course of action here - but I do agree that it isn’t an ideal situation.

I did what you suggested.  Copied my changes over to the newly cloned repo.  And for the past few days it has worked fine. 

But today, it broke again.  I try to push my new commit online and it says it wants to publish the repo, like it doesn’t recognize the one already there.

Why does this keep happening?

That does not sound good :frowning: . Is this just yourself who constantly commits to the master branch and pushes? Using just GitHub Desktop, or other tools as well? Did you make sure you’re still logged in correctly to GitHub? Let us know!

It’s only me.  One computer, I spend about an hour each morning on this project and then commit / push my work.

I’m only using Github Desktop.  It’s on a Mac running High Sierra 10.13.6.

Also, today it worked.  I didn’t change anything from yesterday.  I didn’t even make any code changes, I just launched Github Deskop and hit the Push button and it worked fine.  So, idk.  At least it isn’t broken permanently I guess.  Just sporadically. When it happens again I guess I’ll just wait til the next day and see if it feels like working. :slight_smile:

@bsabiston If you run into this issue again it would be great if you could upload a log file from GitHub Desktop – that should give some more information about what’s happening under the hood.

To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs in Finder (macOS) or Explorer (Windows).

The log files are created daily – please upload a log file as an attachment from a day where you experienced the issue.


Okay,  it happened again today. Here’s the log:

2019-06-03T14:34:56.174Z - info: [ui] [AppStore] loading 4 repositories from store
2019-06-03T14:34:56.177Z - info: [ui] [AppStore] found account: bsabiston (Bob Sabiston)
2019-06-03T14:34:56.738Z - info: [ui] launching: 1.6.6 (Mac OS 10.13.6)
2019-06-03T14:34:56.739Z - info: [ui] execPath: ‘/Applications/GitHub Desktop Desktop Helper’
2019-06-03T14:35:09.617Z - warn: [ui] fetchRepository: ‘bsabiston/04_BattleTank’ returned a 404
2019-06-03T14:35:09.617Z - info: [ui] [AppStore.withAuthenticatingUser] account found for repository: 04_BattleTank - bsabiston (has token)
2019-06-03T14:35:20.832Z - info: [ui] [AppStore] loading 4 repositories from store
2019-06-03T14:35:20.833Z - info: [ui] [AppStore] found account: bsabiston (Bob Sabiston)
2019-06-03T14:35:21.392Z - info: [ui] launching: 1.6.6 (Mac OS 10.13.6)
2019-06-03T14:35:21.393Z - info: [ui] execPath: ‘/Applications/GitHub Desktop Desktop Helper’

Thanks for sharing the log file @bsabiston. My first thought is that there is a caching problem that is causing this issue for you. Here’s what I’d like for you to try:

  1. Close GitHub Desktop
  2. Delete all of the files under ~/Library/Application Support/GitHub Desktop/ (you can do this from the command line by running rm -r "~/Library/Application Support/GitHub Desktop/"
  3. Restart GitHub Desktop – you will need to log in and add your repositories again

Let me know if that does not help with this issue.