Upgrade 1.19.3 to 1.19.4 stuck in loop

[lacostenycoder]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

[Restart and Install doesn't work]

Steps to Reproduce

1. Click squirrel icon
2. It downloads update
3. Click Restart and Install

Expected behavior: [What you expect to happen]
Expect app to restart in new version
Actual behavior: [What actually happens]
App shuts down with no error but doesn't restart.
I launch Atom from command line. Stays at 1.19.3 and starts auto-update download again.
Repeat same cycle. But I get an error when starting atom:

"There was an error checking for updates. The command is disabled and cannot be executed"

If I uncheck "Automatic download updates" then I get the same error in the about page:

Reproduces how often: [What percentage of the time does it reproduce?]
100%

Versions

~ % atom --version
Atom    : 1.19.4
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0

apm  1.18.4
npm  3.10.10
node 6.9.5 x64
python 2.7.10
git 2.14.0

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

[lacostenycoder]

I'm running MacOS 10.11.6 and using homebrew. I ran brew update and that seemed to fix the problem as about page is now reporting the correctly updated version 1.19.4 and no longer stuck in upgrade loop.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!