Niklas Wenzel
Niklas Wenzel
Thanks for checking! That's helpful. (And sorry for making you do unnecessary work.)
@Vlabala Electron is a small team and we're limited in developer time. If you'd like to fix this issue and open a PR, we'd appreciate that!
Just to make sure we're talking about exactly the same code, would you be able to publish a testcase gist using [Electron Fiddle](https://www.electronjs.org/fiddle)?
Thanks! Works for me on macOS. Might be a Linux-only issue.
Question: Does this only happen in development or also when you package, codesign and notarize the app? I've seen similar issues with other macOS APIs in development (e.g. `app.setLoginItemSettings()`), but...
On a related note, #40430 could be useful here. Use different keychain profiles in development and production.
Quoting you from the issue you linked: > This happens on all apps using Chromium, not just Electron apps. Does it happen for Chromium / Google Chrome, too? If yes,...
Thanks! Please share the issue here after you file it. Marking this as `blocked/upstream`. When Chromium fixes it, Electron will pick up the patch in one of the next releases.
I cannot reproduce this issue with the steps given. Try: 1. Rebooting your computer 2. Upgrading Node to v22
Thanks for sharing! That's great. It looks like the change made its way into Chromium 140. This means Electron v38 will pick it up when we upgrade Chromium to the...