Skip to content

fix: always emit executableWillLaunchAtLogin from getLoginItemSettings#51507

Open
trop[bot] wants to merge 2 commits into42-x-yfrom
trop/42-x-y-bp-fix-always-emit-executablewilllaunchatlogin-from-getloginitemsettings--1778014030239
Open

fix: always emit executableWillLaunchAtLogin from getLoginItemSettings#51507
trop[bot] wants to merge 2 commits into42-x-yfrom
trop/42-x-y-bp-fix-always-emit-executablewilllaunchatlogin-from-getloginitemsettings--1778014030239

Conversation

@trop
Copy link
Copy Markdown
Contributor

@trop trop Bot commented May 5, 2026

Backport of #51416

See that PR for details.

Notes: Fixed app.getLoginItemSettings() returning undefined for executableWillLaunchAtLogin on macOS; the property is now always a boolean.

@trop trop Bot requested a review from MarshallOfSound May 5, 2026 20:47
@trop trop Bot added 42-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes labels May 5, 2026
trop Bot and others added 2 commits May 5, 2026 21:10
`Converter<LoginItemSettings>::ToV8` only set `executableWillLaunchAtLogin`
inside the Windows build block, so calling `app.getLoginItemSettings()` on
macOS returned an object where the property was `undefined` rather than
the boolean its type implies.

Move the `executable_will_launch_at_login` field out of the Windows-only
section of `LoginItemSettings` (it keeps its `false` default everywhere)
and unconditionally emit the property in the V8 converter. The value is
still only meaningful on Windows; on other platforms it is always
`false`.

Co-authored-by: Sam Attard <sattard@anthropic.com>
Co-authored-by: Sam Attard <sattard@anthropic.com>
@ckerr ckerr force-pushed the trop/42-x-y-bp-fix-always-emit-executablewilllaunchatlogin-from-getloginitemsettings--1778014030239 branch from 2d12c08 to 356559c Compare May 6, 2026 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

42-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant