-
Notifications
You must be signed in to change notification settings - Fork 28.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX bundle id collides with base electron app, making basic applescript automations open the Electron starter app. #46762
Comments
The app we ship has this in its Info.plist:
Are you sure about that bundle id? |
Hmm you are correct.
returns the correct "com.microsoft.VSCode" but when getting all running non-background processes with
VSCode is reported as
with the id
This is the only electron app on my system that exhibits this behavior. |
I noticed that other electron apps list the executable file in the info.plist as their app name, while VSCode simply uses "Electron" |
Got it, we can change that. |
Risky changes for endgame. Created branch, needs review next week. |
Unfortunately I'm going to have to close this as I can't get a successful update flow working with Squirrel after renaming the executable. I do want this fixed, but not at the cost of breaking the updates for every macOS user. It's too late. 😢 |
Closing as we haven't got more issues with renaming the executable and it is not worth breaking the update flow. |
Attempting to automate windows with applescript causes the base electron app on the system to run, making it difficult to make VSCode an active window. VSCode shares a bundle ID with the base electron app "com.github.electron", which causes OSX System Events to be confused with which app to activate.
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: