Hi Quinn, Thankyou for the update and Yes, I am trying this as part of authorisation plug-in only. As you suggested, I tried separating out the bluetooth advertising from my daemon and invoke the bluetooth agent pre-login and perform advertising. Can you please help me understand when exactly this daemon gets invoked like is it only after restart or even at logout and login will I be able to invoke agent through daemon (how to control it)?

HI Quinn, When using the above created BLEAdvertising app by adding it to the LaunchDaemon (in logged in session not pre-login), once advertising started when I try to unload the app using "sudo launchctl unload /Library/LaunchDaemons/com.abc.myBLEapp.plist" it is stoping advertising as expected. But when I try to load again using "sudo launchctl load /Library/LaunchDaemons/com.abc.myBLEapp.plist" it is not starting advertising, to get the advertising I have to perform "sudo pkill bluetoothd". Am I missing anything to get the advertising start again when I load my app through launchctl? As pkill will kill and restart the bluetooth process, due to this if there are any other ble connected devices they need to get reconnected, so Is using pkill bluethoothd a proper approach?