[GH-ISSUE #519] on systemstart Ventura shows me always added to login items

kerem commented

2026-03-03 01:11:48 +03:00

Owner

Originally created by @Frankapple on GitHub (Oct 28, 2022).
Original GitHub issue: https://github.com/Clipy/Clipy/issues/519

that issue is since Ventura

Originally created by @Frankapple on GitHub (Oct 28, 2022). Original GitHub issue: https://github.com/Clipy/Clipy/issues/519 that issue is since Ventura

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@zygiboos commented on GitHub (Oct 29, 2022):

same here

@zygiboos commented on GitHub (Oct 29, 2022): same here

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@bazilinskyy commented on GitHub (Oct 30, 2022):

Same here

@bazilinskyy commented on GitHub (Oct 30, 2022): Same here

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@algkmn commented on GitHub (Nov 1, 2022):

same here

@algkmn commented on GitHub (Nov 1, 2022): same here

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@bopeterson commented on GitHub (Nov 8, 2022):

same here

@bopeterson commented on GitHub (Nov 8, 2022): same here

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@z0r3f commented on GitHub (Nov 11, 2022):

+1

@z0r3f commented on GitHub (Nov 11, 2022): +1

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@somenugget commented on GitHub (Nov 12, 2022):

+1

@somenugget commented on GitHub (Nov 12, 2022): +1

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@Bon3863 commented on GitHub (Nov 18, 2022):

same here
MacOS 13.0.1 on MacBookPro 2019

@Bon3863 commented on GitHub (Nov 18, 2022): same here MacOS 13.0.1 on MacBookPro 2019

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@c-hoeger commented on GitHub (Nov 22, 2022):

I am not a Swift/macOS programmer, so I won't provide a fixed version, since I don't know if the solution is completely valid. I managed to build from the develop branch after a huge amount of trial and error and finally found a solution applying the following patch:

diff --git a/Clipy/Sources/AppDelegate.swift b/Clipy/Sources/AppDelegate.swift
index af0736f..11ae80c 100644
--- a/Clipy/Sources/AppDelegate.swift
+++ b/Clipy/Sources/AppDelegate.swift
@@ -153,7 +153,7 @@ class AppDelegate: NSObject, NSMenuItemValidation {

     private func toggleAddingToLoginItems(_ isEnable: Bool) {
         let appPath = Bundle.main.bundlePath
-        LoginServiceKit.removeLoginItems(at: appPath)
+        // LoginServiceKit.removeLoginItems(at: appPath)
         guard isEnable else { return }
         LoginServiceKit.addLoginItems(at: appPath)
     }

@c-hoeger commented on GitHub (Nov 22, 2022): I am not a Swift/macOS programmer, so I won't provide a fixed version, since I don't know if the solution is completely valid. I managed to build from the develop branch after a huge amount of trial and error and finally found a solution applying the following patch: ```diff diff --git a/Clipy/Sources/AppDelegate.swift b/Clipy/Sources/AppDelegate.swift index af0736f..11ae80c 100644 --- a/Clipy/Sources/AppDelegate.swift +++ b/Clipy/Sources/AppDelegate.swift @@ -153,7 +153,7 @@ class AppDelegate: NSObject, NSMenuItemValidation { private func toggleAddingToLoginItems(_ isEnable: Bool) { let appPath = Bundle.main.bundlePath - LoginServiceKit.removeLoginItems(at: appPath) + // LoginServiceKit.removeLoginItems(at: appPath) guard isEnable else { return } LoginServiceKit.addLoginItems(at: appPath) } ```

kerem commented

2026-03-03 01:11:49 +03:00

Author

Owner

@bvandergiessen commented on GitHub (Dec 6, 2022):

This solution by @arubdesu worked for me #517 (comment)

Unfortunately, according to that post, it isn't a solution:

generating a new build seems to be the only fix, short of Apple stopping their notification behavior.

@bvandergiessen commented on GitHub (Dec 6, 2022): > This solution by @arubdesu worked for me [#517 (comment)](https://github.com/Clipy/Clipy/issues/517#issuecomment-1268009048) Unfortunately, according to that post, it isn't a solution: > generating a new build seems to be the only fix, short of Apple stopping their notification behavior.

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@ngaretou commented on GitHub (Dec 6, 2022):

Workaround for this:

Open Clipy preferences.
Uncheck 'launch at login'
Log out of macOS
On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again.
- This is the problem, where its 'run at startup' method is deprecated, as noted above.
- If you directly add Clipy to the Login Items now, it will run one time, but because you said not to run it every time, it will remove itself and never run after that.
Now open Automator.
New Document
Application
Utilities on left column
Run Shell Script on right column
There paste open -a Clipy
Save that as "Clipy Run" in Applications folder and Close
Now add your Clipy Run Automator app to Login Items.

@ngaretou commented on GitHub (Dec 6, 2022): Workaround for this: - Open Clipy preferences. - Uncheck 'launch at login' - Log out of macOS - On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again. - This is the problem, where its 'run at startup' method is deprecated, as noted above. - If you directly add Clipy to the Login Items now, it will run one time, but because you said not to run it every time, it will remove itself and never run after that. - Now open Automator. - New Document - Application - Utilities on left column - Run Shell Script on right column - There paste `open -a Clipy` - Save that as "Clipy Run" in Applications folder and Close - Now add your Clipy Run Automator app to Login Items.

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@Bon3863 commented on GitHub (Dec 7, 2022):

Great ! @ngaretou
It works fine, thank you.

@Bon3863 commented on GitHub (Dec 7, 2022): Great ! @ngaretou It works fine, thank you.

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@marcora commented on GitHub (Dec 17, 2022):

Please fix this issue!

@marcora commented on GitHub (Dec 17, 2022): Please fix this issue!

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@retrogamer0815 commented on GitHub (Dec 20, 2022):

@ngaretou Thanks, worked for me too!

@retrogamer0815 commented on GitHub (Dec 20, 2022): @ngaretou Thanks, worked for me too!

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@seraphyn commented on GitHub (Jan 27, 2023):

Would be great to provide a fix in a new release.
Does someone forked the project?

@seraphyn commented on GitHub (Jan 27, 2023): Would be great to provide a fix in a new release. Does someone forked the project?

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@bslmac commented on GitHub (Jan 30, 2023):

Merci/Thanks @ngaretou, facile et simple à mettre en place. Souhaitons une version à jour bientôt de la part des guerriers du code! / easy and simple to set up. Hope for an updated version soon from the code warriors!

@bslmac commented on GitHub (Jan 30, 2023): Merci/Thanks @ngaretou, facile et simple à mettre en place. Souhaitons une version à jour bientôt de la part des guerriers du code! / easy and simple to set up. Hope for an updated version soon from the code warriors!

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@bvandergiessen commented on GitHub (Jan 31, 2023):

@Econa77 Do you think you could create a new build with this bugfix (the one proposed in the comment above)?

@bvandergiessen commented on GitHub (Jan 31, 2023): @Econa77 Do you think you could create a new build with this bugfix (the one proposed in [the comment above](https://github.com/Clipy/Clipy/issues/519#issuecomment-1323899822))?

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@c-hoeger commented on GitHub (Jan 31, 2023):

I for myself now switched to https://github.com/p0deje/Maccy

@c-hoeger commented on GitHub (Jan 31, 2023): I for myself now switched to https://github.com/p0deje/Maccy

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@seraphyn commented on GitHub (Jan 31, 2023):

I for myself now switched to https://github.com/p0deje/Maccy

Same on my side
Seems like the development stopped a few months ago

@seraphyn commented on GitHub (Jan 31, 2023): > I for myself now switched to https://github.com/p0deje/Maccy Same on my side Seems like the development stopped a few months ago

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@rickogorman commented on GitHub (Feb 9, 2023):

@ngaretou Thanks for that tip. Using your logic, I used Lingon X to add the command open -a Clipy as a launch agent, seems to work as well, another option for users.

@rickogorman commented on GitHub (Feb 9, 2023): @ngaretou Thanks for that tip. Using your logic, I used Lingon X to add the command `open -a Clipy` as a launch agent, seems to work as well, another option for users.

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@JimDanner commented on GitHub (Mar 22, 2023):

As a variation on this workaround by @ngaretou, after the first steps

Workaround
* Open Clipy preferences.
* Uncheck 'launch at login'
* Log out of macOS
* On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again.

I added a launch agent (instead of using Automator) to do the starting at login. In ~/Library/LaunchAgents/ I created a file com.jim.clipy.plist with the following contents:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>com.jim.clipy</string>
	<key>RunAtLoad</key>
	<true/>
	<key>ProgramArguments</key>
	<array>
		<string>open</string>
		<string>-a</string>
		<string>Clipy</string>
	</array>
</dict>
</plist>

This also works.

@JimDanner commented on GitHub (Mar 22, 2023): As a variation on [this workaround](https://github.com/Clipy/Clipy/issues/519#issuecomment-1339650815) by @ngaretou, after the first steps > Workaround > * Open Clipy preferences. > * Uncheck 'launch at login' > * Log out of macOS > * On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again. I added a launch agent (instead of using Automator) to do the starting at login. In ~/Library/LaunchAgents/ I created a file `com.jim.clipy.plist` with the following contents: ```xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.jim.clipy</string> <key>RunAtLoad</key> <true/> <key>ProgramArguments</key> <array> <string>open</string> <string>-a</string> <string>Clipy</string> </array> </dict> </plist> ``` This also works.

kerem commented

2026-03-03 01:11:50 +03:00

Author

Owner

@ghost commented on GitHub (May 26, 2023):

Workaround for this:

Open Clipy preferences.

Uncheck 'launch at login'

Log out of macOS

On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again.

This is the problem, where its 'run at startup' method is deprecated, as noted above.

If you directly add Clipy to the Login Items now, it will run one time, but because you said not to run it every time, it will remove itself and never run after that.

Now open Automator.

New Document

Application

Utilities on left column

Run Shell Script on right column

There paste open -a Clipy

Save that as "Clipy Run" in Applications folder and Close

Now add your Clipy Run Automator app to Login Items.

I am not particularly familiar with Automator but I am usually game for new experiences especially when there are nice clear instructions like these, however, when I open Automator I do not see "New Document" anywhere. There is a list of options such as "Workflow", "Application", "Quick Action", "Folder Actions" one of which I have to choose to continue. So I chose "Application" since it is the next step in the instructions anyway. I then see and choose "Utilities" and then choose "Run Shell Script" but I can find no way to paste "open -a Clipy". Did Automator change since these directions were written? Thanks

@ghost commented on GitHub (May 26, 2023): > Workaround for this: > > * Open Clipy preferences. > * Uncheck 'launch at login' > * Log out of macOS > * On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again. > > * This is the problem, where its 'run at startup' method is deprecated, as noted above. > * If you directly add Clipy to the Login Items now, it will run one time, but because you said not to run it every time, it will remove itself and never run after that. > * Now open Automator. > * New Document > * Application > * Utilities on left column > * Run Shell Script on right column > * There paste `open -a Clipy` > * Save that as "Clipy Run" in Applications folder and Close > * Now add your Clipy Run Automator app to Login Items. I am not particularly familiar with Automator but I am usually game for new experiences especially when there are nice clear instructions like these, however, when I open Automator I do not see "New Document" anywhere. There is a list of options such as "Workflow", "Application", "Quick Action", "Folder Actions" one of which I have to choose to continue. So I chose "Application" since it is the next step in the instructions anyway. I then see and choose "Utilities" and then choose "Run Shell Script" but I can find no way to paste "open -a Clipy". Did Automator change since these directions were written? Thanks

kerem commented

2026-03-03 01:11:51 +03:00

Author

Owner

@rangedsp commented on GitHub (Jun 7, 2023):

@jmilt7 you should be able to achieve the same thing using the 'Launch application' workflow, instructions here:
https://learn.adafruit.com/launch-deck-trellis-m4/app-launching

@rangedsp commented on GitHub (Jun 7, 2023): @jmilt7 you should be able to achieve the same thing using the 'Launch application' workflow, instructions here: https://learn.adafruit.com/launch-deck-trellis-m4/app-launching

kerem commented

2026-03-03 01:11:51 +03:00

Author

Owner

@ghost commented on GitHub (Jun 8, 2023):

@jmilt7 you should be able to achieve the same thing using the 'Launch application' workflow, instructions here:
https://learn.adafruit.com/launch-deck-trellis-m4/app-launching

Thanks. Haven't tried this yet as I am debating whether just closing the notification once a day or once every couple of days is a big inconvenience or not in the whole scheme of things but I do like the idea of playing with Automator as I have never tried it before and I like to try new things. So thanks again for this.

@ghost commented on GitHub (Jun 8, 2023): > @jmilt7 you should be able to achieve the same thing using the 'Launch application' workflow, instructions here: > https://learn.adafruit.com/launch-deck-trellis-m4/app-launching Thanks. Haven't tried this yet as I am debating whether just closing the notification once a day or once every couple of days is a big inconvenience or not in the whole scheme of things but I do like the idea of playing with Automator as I have never tried it before and I like to try new things. So thanks again for this.

Rows
Columns

[GH-ISSUE #519] on systemstart Ventura shows me always added to login items #337