[Bug]: auto dark mode wrong behavior

[rainbowflesh]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

1. When system change to light/dark mode with VS Code running, extension will notify theme changed and pop up reload dialog; but after restart, the "config is changed" dialog will pop up again with change back to opposite theme.
2. When system change to light/dark mode without VS Code running, extension won't prompt change to light/dark mode.

Expected Behavior

A light/dark mode check after VS Code start up will help?

Steps To Reproduce

1. close vscode.
2. change system theme.
3. run vscode.

Environment

- OS: win11
- VSCode: newest release
- Extension: alot
- Theme: rosepine

Anything else?

{
"vscode_vibrancy.theme":"light",
"vscode_vibrancy.preferedLightTheme":"light",
"vscode_vibrancy.preferedDarkTheme":"dark",
"window.autoDetectColorScheme":true
}

[MrOxMasTer]

The github theme is breaking too

[LiPingYen]

The solarized dark + is broken.

[zedle]

Same here with Catppuccin Mocha. If I set the theme again it will work until I load a new folder, reload the workspace, or restart vscode, then it breaks again.

[Fefedu973]

Same

[LouisRaverdy]

Same issue here, the only workaround is downgrading the version on install.
Waiting for a fix

[illixion]

Apologies all, pushed some faulty code, version .31 has the fix

[LouisRaverdy]

Nice ! Thank you for your great extension !

[illixion]

The Vibrancy theme setting needs to be restored to what it was before as the previous value would've been lost, unfortunately

[Fefedu973]

The Vibrancy theme setting needs to be restored to what it was before as the previous value would've been lost, unfortunately

Yup. Only issue. It seems that now the window control isn't working (cannot click on the maximize button and cannot snap the window on the sides)

[illixion]

Yup. Only issue. It seems that now the window control isn't working (cannot click on the maximize button and cannot snap the window on the sides)

If you’re on Windows, you may be encountering this bug: #140