-
Notifications
You must be signed in to change notification settings - Fork 869
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
Desktop ask to control System Events on macOS on first run #753
Comments
Did you always get that or it was after a specific commit? On Windows it doesn't need any special permission. It doesn't even ask for Administrator permission unless you install it for the whole system. |
I get it when using desktop from the .dmg. I'll see what I can find out about it. |
+1 to @olizilla 's experience -- same thing happened to me, also downloaded as .dmg . |
+1. Also, from UX perspective the app is opened in background and put into Mac menu bar. However, the app in launch bar is not opened (there is not a dot under the icon - indicating the app is opened). I tried to open the app multiple times till I realised that I can access the app from menu bar. It would be great to see at least a message every time you try to open the app saying "IPFS Desktop is already running. You can access the app from menu bar." |
Well, we only allow one instance at a time and we tell the user if they try to launch Desktop more than one time. At least on Windows it is working, but I see macOS has different mechanisms. @olizilla @fsdiogo could you check that please? |
Closing this: we will keep asking to control System Events, otherwise we can't add IPFS Desktop as a login item 😄 Source: https://github.com/Teamwork/node-auto-launch#applescript-default Their alternative (Launch Agent) has some worse cons (such as leaving files behind when uninstalling). |
On first run on macOS, we get this dialog
We should see if we can remove the need for the System Events, as I don't think we're doing anything that directly needs it.
The text was updated successfully, but these errors were encountered: