It looks like that the UX for embedded LaunchDaemons is a "bit" broken in macOS 13.1 (at least). And the UX of the Login Items pane is also quite broken.
I have a simple app bundle with one launch agent and one launch daemon (both embedded).
- If I try to register the launch agent, it works. If I try to unregister it, it works,
- If i try to register the launch daemon, I can allow it using the system notification.
- if I try to register the launch daemon and close the system notification, I can't find a way to allow it in the Settings > General > Login Items pane. If I try to register it again, I don't get a system notification to allow it.
- if I try to register the launch daemon and close the system notification and I then try to register the launch agent, it fails and requires approval, which I can't grant because the system notification is AWOL.
- if I disable the entry in the Login Items pane for the app, usually, I see disabled items being added for the launch agent and launch daemon while the application is removed from the list.
- when I delete the app on Disk, the entries sometimes stay in the Login Items pane, sometimes disappear. Sometimes, quitting Setting.app and opening it again solves the issue, sometimes it doesn't.
- if I try to click on the (i) button for either the Launch Agent or Launch Daemon entry, it does not show them in the Finder whereas the app is still there. The (i) button works correctly for an item in ~/Library/LaunchAgents.
Basically, the whole UX seems broken and is totally confusing for both the end user and the developer.
[Q] Is this how this is expected to work?