desktop: Error: spawn git.exe ENOENT

Description

Upgraded to Desktop v1.3, got this error immediately after it opened: image

Version

  • GitHub Desktop: 1.3.0
  • Operating system: Windows

Steps to Reproduce

  1. Update Github Desktop to v1.3
  2. Get Error

Logs

No errors in the logs

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 10
  • Comments: 31 (14 by maintainers)

Most upvoted comments

Thanks to everyone who has reported this. We believe this is related to missing repositories and the new repository indicator feature.

What’s happening here is:

  • a repository that Desktop was previously tracking is now missing from disk
  • the upgrade triggers the new repository indicators
  • in the background the app tries to check this missing repository
  • it doesn’t handle the ENOENT error (because it’s trying to be run in a directory that doesn’t exist)
  • this is being done outside our existing error infrastructure, so it displays to the user

As a workaround, you can remove these missing repositories on disk - it might take some time to click through the list and find the problem repository.

We’re working on a fix now to handle this error and not display any UI. Stay tuned.

1.3.1 has been published, and should address the issue of background updates.

We are also tracking #5289 which you might encounter when you manually switch to a repository that’s been removed outside Desktop, and that will hopefully go into the next update.

Same problem on macOS, getting spawn /Applications/GitHub Desktop.app/Contents/Resources/app/git/bin/git ENOENT error after upgraded.

Whoa that was fast - fixed for me too on Win10 x64 🥇

Just doing a brain dump of the status of this issue:

  • this has been noticed by users on macOS and Windows
  • we haven’t upgraded Git as part of this recent release
  • the upgrade from Electron 1.8.x to 2.0.x resulted in an NodeJS (embedded in Electron) from 8.2.1 to 8.9.3

I haven’t been able to reproduce this on either macOS or Windows, but @iAmWillShepherd has stumbled upon it so we’re digging into what’s changed.

Window 10 x64 immediately after updating to 1.3. The file exists. I have uninstalled and reinstalled and still get the same error.

Fixed in 1.3.1. Thanks, team!

@shiftkey I just pulled the latest update after finding this thread; v1.3.1 does indeed fix the issue for me. Thanks for the great quick turnaround!