electron: Disable setLoginItemSettings -> openAtLogin not working

  • Electron version: 1.7.9
  • Operating system: macOS High Sierra (10.13)

Expected behavior

app.setLoginItemSettings({ openAtLogin: false }); should disable auto start.

Actual behavior

app.setLoginItemSettings({ openAtLogin: true }); adds app to auto start as expected. However setting it to false does not remove it. On macOS 10.12 it was working as expected.

How to reproduce

In main or renderer run the following code

console.log(app.getLoginItemSettings().openAtLogin); // either true or false if it has been set before
app.setLoginItemSettings({ openAtLogin: true }); 
console.log(app.getLoginItemSettings().openAtLogin); // true
app.setLoginItemSettings({ openAtLogin: false });
console.log(app.getLoginItemSettings().openAtLogin); // true

I’ve provided a test repo here:

$ git clone https://github.com/adlk/openAtLogin-issue -b master
$ npm install
$ npm start || electron .

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 18
  • Comments: 35 (6 by maintainers)

Most upvoted comments

any updates on this issue

@mickours this feature is not available on Linux based on docs, LOL

Bummer, still broken over 6 months later 😢

Any progress on this?

I’m also experiencing this with Now (version 4.0.19).

macOS 10.14.4

Note that this bug also impact Linux platform with Electron 1.8.2, not only MacOS.

Any progress on this? Came here from https://github.com/zeit/now-desktop/issues/422

Having this issue on a brand new clean install of newest MacOS High Sierra.

This is a workaround that works for me:

require('child_process').exec(`osascript -e 'tell application "System Events" to delete login item "Electron"'`)

In the command above, replace Electron with your application name.

I can try to take a look at this soon

I did a bit research, and it’s probably because https://developer.apple.com/documentation/coreservices/1443926-lssharedfilelistcreate is deprecated.

have the same issue with electron 1.6.11 also High Sierra

I also ran into this bug. Awaiting fix (:

@seanlerner Interesting approach. I will test here. thanks