Close Menu
geekfence.comgeekfence.com
    What's Hot

    Francis Bacon and the Scientific Method

    April 19, 2026

    War in the Middle East, Damaged Data Centers, and Cloud Disruptions

    April 19, 2026

    How Much Coding Is Required To Work in AI and LLM-related Jobs?

    April 19, 2026
    Facebook X (Twitter) Instagram
    • About Us
    • Contact Us
    Facebook Instagram
    geekfence.comgeekfence.com
    • Home
    • UK Tech News
    • AI
    • Big Data
    • Cyber Security
      • Cloud Computing
      • iOS Development
    • IoT
    • Mobile
    • Software
      • Software Development
      • Software Engineering
    • Technology
      • Green Technology
      • Nanotechnology
    • Telecom
    geekfence.comgeekfence.com
    Home»iOS Development»How to launch a macOS app at login?
    iOS Development

    How to launch a macOS app at login?

    AdminBy AdminApril 19, 2026No Comments4 Mins Read1 Views
    Facebook Twitter Pinterest LinkedIn Telegram Tumblr Email
    How to launch a macOS app at login?
    Share
    Facebook Twitter LinkedIn Pinterest Email


    In this tutorial I’ll show you how to launch a completely sandboxed macOS application on system startup written in Swift.

    Update: you should simply add the LaunchAtLogin library to your project. It’ll take care of everything and it has some other cool utility features.

    Project setup

    Let’s start this tutorial by creating a new Xcode project with a macOS app template. Name it for example MainApplication, use storyboards and of course select Swift as the default language, we don’t need tests for this project at all.

    Now that we have the main application target, there is this nice little function available called SMLoginItemSetEnabled. With that function you can register an application bundle identifier to auto start when the user logs in, but you can not register your own app identifier. Sounds crazy, huh? 😜

    You can register a bundle identifier embedded into your main application to get auto-launched by the system. To do this you will have to create a new launcher application which will be launched later by your main application.

    You also have to code sign your application with your Developer ID, otherwise it won’t start after you log in to macOS. Sandboxing is a crucial part of the process, so make sure that you follow every instruction carefully.

    Targets & configurations

    Create a new target inside your current project. Name this new target for example LauncherApplication. Enable sandbox and code signing for both targets (main and launcher apps) under the Signing & Capabilities tab. For the LauncherApplication target in the build settings set skip install to yes.

    How to launch a macOS app at login?

    For the launcher app add a new entry to the Info.plist file: Application is background only with the value: yes. This will set your application as a background app, we don’t really need user interface for a launcher tool, right?

    Background only

    Add a new copy file build phase to your main application target to copy your launcher application into the bundle. The destination should be wrapper and the subpath should be Contents/Library/LoginItems.

    Copy files

    Link the ServiceManagement.framework to your main application and double check that the launcher app is embedded into your main application.

    Frameworks

    From the LauncherApplication‘s storyboard file delete your window and your view controller, also you can remove the ViewController.swift file from this target. This is a background app after all, so we don’t need these stupid things to lay around.

    Creating the launcher programmatically

    Somewhere in your main application you have to register your launcher application’s identifier. When your main application starts you have to kill the launcher application if it’s still running. You can do this by sending a notification to that specific app with the NSDistributedNotificationCenter class.

    import Cocoa
    import ServiceManagement
    
    extension Notification.Name {
        static let killLauncher = Notification.Name("killLauncher")
    }
    
    @NSApplicationMain
    class AppDelegate: NSObject {}
    
    
    extension AppDelegate: NSApplicationDelegate {
    
        func applicationDidFinishLaunching(_ aNotification: Notification) {
    
            let launcherAppId = "com.tiborbodecs.LauncherApplication"
            let runningApps = NSWorkspace.shared.runningApplications
            let isRunning = !runningApps.filter { 
                $0.bundleIdentifier == launcherAppId 
            }.isEmpty
    
            SMLoginItemSetEnabled(launcherAppId as CFString, true)
    
            if isRunning {
                DistributedNotificationCenter.default().post(
                    name: .killLauncher, 
                    object: Bundle.main.bundleIdentifier!
                )
            }
        }
    }
    

    In the launcher application you have to start your main application if it’s not running already. That’s it. You should also subscribe for the notifications from the main app to terminate if the launcher is not needed anymore.

    import Cocoa
    
    extension Notification.Name {
        static let killLauncher = Notification.Name("killLauncher")
    }
    
    @NSApplicationMain
    class AppDelegate: NSObject {
    
        @objc func terminate() {
            NSApp.terminate(nil)
        }
    }
    
    extension AppDelegate: NSApplicationDelegate {
    
        func applicationDidFinishLaunching(_ aNotification: Notification) {
    
            let mainAppIdentifier = "com.tiborbodecs.MainApplication"
            let runningApps = NSWorkspace.shared.runningApplications
            let isRunning = !runningApps.filter { 
                $0.bundleIdentifier == mainAppIdentifier 
            }.isEmpty
    
            if !isRunning {
                DistributedNotificationCenter.default().addObserver(
                    self, 
                    selector: #selector(self.terminate), 
                    name: .killLauncher, 
                    object: mainAppIdentifier
                )
    
                let path = Bundle.main.bundlePath as NSString
                var components = path.pathComponents
                components.removeLast()
                components.removeLast()
                components.removeLast()
                components.append("MacOS")
                components.append("MainApplication") //main app name
    
                let newPath = NSString.path(withComponents: components)
    
                NSWorkspace.shared.launchApplication(newPath)
            }
            else {
                self.terminate()
            }
        }
    }
    

    That’s it, we’re ready to launch. Export your main application and here is the most important thing: code sign it with your Developer ID. Start it, close it, log out and back into the system. Hopefully your main application will be running again.



    Source link

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email

    Related Posts

    ios – Xcode can’t find headers file from added frameworks

    April 18, 2026

    Self sizing cells with rotation support

    April 14, 2026

    swift – Flutter iOS: USSD code with * and # not launching in phone dialer (works on Android)

    April 13, 2026

    UICollectionView cells with circular images plus rotation support

    April 9, 2026

    ios darkmode – Popovers in iOS 26 display wrong system colors and do not change when user switches light/dark mode

    April 8, 2026

    SwiftButler | Cocoanetics

    April 4, 2026
    Top Posts

    Understanding U-Net Architecture in Deep Learning

    November 25, 202530 Views

    Hard-braking events as indicators of road segment crash risk

    January 14, 202625 Views

    Redefining AI efficiency with extreme compression

    March 25, 202624 Views
    Don't Miss

    Francis Bacon and the Scientific Method

    April 19, 2026

    In 1627, a year after the death of the philosopher and statesman Francis Bacon, a…

    War in the Middle East, Damaged Data Centers, and Cloud Disruptions

    April 19, 2026

    How Much Coding Is Required To Work in AI and LLM-related Jobs?

    April 19, 2026

    How to Make a Claude Code Project Work Like an Engineer

    April 19, 2026
    Stay In Touch
    • Facebook
    • Instagram
    About Us

    At GeekFence, we are a team of tech-enthusiasts, industry watchers and content creators who believe that technology isn’t just about gadgets—it’s about how innovation transforms our lives, work and society. We’ve come together to build a place where readers, thinkers and industry insiders can converge to explore what’s next in tech.

    Our Picks

    Francis Bacon and the Scientific Method

    April 19, 2026

    War in the Middle East, Damaged Data Centers, and Cloud Disruptions

    April 19, 2026

    Subscribe to Updates

    Please enable JavaScript in your browser to complete this form.
    Loading
    • About Us
    • Contact Us
    • Disclaimer
    • Privacy Policy
    • Terms and Conditions
    © 2026 Geekfence.All Rigt Reserved.

    Type above and press Enter to search. Press Esc to cancel.