As Jens suggested in another thread, launchd is likely too low-level.
Finally, there is Tim Schroeder’s “Launch At Login Project” which enables a sandboxed app to launch itself. <http://blog.timschroeder.net/2012/07/03/the-launch-at-login-sandbox-project <http://blog.timschroeder.net/2012/07/03/the-launch-at-login-sandbox-project>/> This uses the SMLoginItemSetEnabled call in a separate process. I wish someone at Apple would step in here and provide a little direction on which is the best way for an app to launch _itself_ at login. > On Apr 19, 2016, at 2:43 PM, Jeff Szuhay <j...@szuhay.org > <mailto:j...@szuhay.org>> wrote: > > Again, I jumped the gun. > > The preferred way seems to be through the use of launchd > <http://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html > > <http://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html> > > > >>>> On Apr 19, 2016, at 2:01 PM, Jens Alfke <j...@mooseyard.com >>>> <mailto:j...@mooseyard.com>> wrote: >>>> >>>> One of my companies’ apps has a “Launch at login” pref, which no longer >>>> works in OS X 10.11. I’m not surprised, since the existing code implements >>>> this by writing into loginwindow’s user defaults :-p _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
