Add “Launch at Login” functionality to your macOS app in seconds
It's usually quite a convoluted and error-prone process to add this. No more!
- macOS 10.12+
- Xcode 11+
- Swift 5+
Add a new "Run Script Phase" below "Embed Frameworks" in "Build Phases" with the following:
Use it in your app:
import LaunchAtLogin print(LaunchAtLogin.isEnabled) //=> false LaunchAtLogin.isEnabled = true print(LaunchAtLogin.isEnabled) //=> true
No need to store any state to UserDefaults.
Note that the Mac App Store guidelines requires “launch at login” functionality to be enabled in response to a user action. This is usually solved by making it a preference that is disabled by default. Many apps also let the user activate it in a welcome screen.
How does it work?
The framework bundles the helper app needed to launch your app and copies it into your app at build time.
My app doesn't show up in “System Preferences › Users & Groups › Login Items”
This is the expected behavior, unfortunately.
My app doesn't launch at login when testing
This is usually caused by having one or more older builds of your app laying around somewhere on the system, and macOS picking one of those instead, which doesn't have the launch helper, and thus fails to start.
Some things you can try:
- Bump the version & build of your app so macOS is more likely to pick it.
- Delete the
- Ensure you don't have any other builds laying around somewhere.
Some helpful Stack Overflow answers:
Can you support CocoaPods?
CocoaPods used to be supported, but it did not work well and there was no easy way to fix it, so support was dropped. Even though you mainly use CocoaPods, you can still use Carthage just for this package without any problems.
I'm getting a
'SMCopyAllJobDictionaries' was deprecated in OS X 10.10 warning
Apple deprecated that API without providing an alternative. Apple engineers have stated that it's still the preferred API to use. I plan to use it as long as it's available. There are workarounds I can implement if Apple ever removes the API, so rest assured, this module will be made to work even then. If you want to see this resolved, submit a Feedback Assistant report with the following text. There's unfortunately still no way to suppress warnings in Swift.