On macOS 15 Sequoia, there is a new Legacy Background Tasks toggle in System Settings > Login Items & Extensions. It seems to initially appear (in an "on" state) when an app tries to install a launchd job and places a launch plist in /Library/LaunchDaemons. I have not found any effects of turning this toggle off. I still seem to be able to happily use launchctl bootstrap and launchctl bootout, for example. What does this toggle do? Is there a WWDC session or documentation I haven't found yet?

I was trying out SMAppService on macOS Ventura to register LaunchDaemons and LaunchAgents. Apparently I didn't get it quite right 🙈 So now I am in a situation where I registered a LaunchDaemons (it showed up in System Settings > General > Login Items) and did not throw an error on registering, but it doesn't really work and I am not able to unregister it. SMAppService.unregister() returns SMAppServiceErrorDomain Code 113 "Could not find the specified service". The SMAppService instance I am trying to use for unregistering was created the same way that I registered, using SMAppService.daemon(plistName: "some.plist"). Is there any way to reset the state or remove the broken daemon config manually? I tried removing all copies of my app from the system and rebooting, but that didn't clean it out.

In the footsteps of the old The Rules for Full Disk Access - https://developer.apple.com/forums/thread/107546 thread, I am a little confused about the inheritance rules for Accessibility user consent (System Preferences Security & Privacy Privacy Accessibility) for helper tools contained in an app bundle. In my tests, user consent for Full Disk Access is inherited by helper tools (and app bundles) if the user permits Full Disk Access for the containing app bundle. Other categories, such as Screen Recording, also show this behavior. However Accessibility seems to be different: Consent is not inherited by helper tools and app bundles. Is that the intended behavior / documented anywhere? Or am I missing something?