-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Secret Agent doesn't run at startup #555
Comments
I have this problem too. This is what I get, if I try to run the agent from the terminal: macOS 14.5 on a M3 Pro Chip |
Any chance to get this fixed? I really liked the app on the previous devices :) |
Are you folks seeing this consistently every reboot? I'm aware of some ongoing (hard to debug) issues around it relaunching after an update, but not so much every launch. |
I think on the first run I shortly saw the Agent on the Activity Monitor. It then exited. After the first run the Agent never appeared again on the Activity Monitor and if I try to run it, I will get that error message. But I could run it as root (but then it does not work either) |
I closed the app multiple times completely and also did a reboot |
yes, it's there and activated |
Any news? |
Yes, this is ongoing and there is a login item for secretive, and it's enabled. but it does not run (or doesn't stay running; either way) this is still an issue |
It appears that it has started working, that is, app now starts when macOS restarts. I am not sure of what changes if any were made. |
I've installed Secretive, and followed the prompt to install Secret Agent, but it does not launch at startup, only when I manually open Secretive. This causes ssh connections to fail instantly. (ssh: connect to host xxxxx port 22: Undefined error: 0)
I have tried running the 'Setup Secretive' several times, but every time I reboot my machine, Secret Agent does not run automatically. I see no possible option to add Secret Agent manually to my 'login items' and am at a loss of what to do next.
The text was updated successfully, but these errors were encountered: