Post not yet marked as solved
Thanks. I've filed it as FB8600589.
It's unfortunate there's no workaround though. Since I need to support existing macOS versions, my only choice seems to be creating another process just for posting notifications and having it be non-XPC so I can name it something reasonable.
Post not yet marked as solved
NM. Seems like one of the answers in this thread did the trick: https://developer.apple.com/forums/thread/66418
In particular, the part about editing ~/Library/Preferences/com.apple.security.plist and removing the extra entries. codesign is now down to a second or under.
Thought having a quick commandline thing I could call to fix it as needed would be more convenient. Also, just curious.Also, it seems that what triggered this recently was that a code path changed. Previously, SMLoginItemSetEnabled was being called every time to unregister before registering but that a changed mixed things up such that it wasn't always the case.Thanks.
Note that the app isn't sandboxed.Will doing 'launchctl remove' do the same as SMLoginItemSetEnabled? I have been doing that and it doesn't seem to work. Is there some cache somewhere I can ****?
Ok, was having various problems with it until I started using LSRegisterURL as SMLoginItemSetEnabled wasn't launching my helper. Things seem a bit more convoluted now but at least I have a working version so I know it's possible. Not fond of "hidden" login items, preferring to have an explicit entry in the login items user interface but I guess you can't have everything.
Thanks for the clarification. The helper (which is the XPC server in this case) is indeed the process which is the login item so I'll look into the example you sent.A couple of quick questions, though:- My app is not sandboxed. Aside from the first step in the README which won't apply to me, are there any other caveats?- Will this work when the app is first installed or anytime the helper is killed? The helper will be launched manually by the outer app and not via login items.
Post not yet marked as solved
I need to either show or process files in folders. If the user selects one of these folders, I want to reflect what Finder shows. I already do special handling for the Trash but it would be nice if there was a way to know about/handle these cases without having to stumble on to each instance myself.
Post not yet marked as solved
Is there any sort of list (or even better, API) that enumerates these cases?
Post not yet marked as solved
FB6115774 for me.Was also told it was intentional and to use SecACLUpdateAuthorizations(), which, as far as I can tell, ultimately requires SecTrustedApplicationCreateFromPath(). Even if there is a newer way to accomplish this, the docs don't state what that is and since it was marked unavailable across even older versions of macOS, this will end up breaking things there.
