My situtation: I recently added AssociatedBundleIdentifiers in launchd plist and see the result that my app's name is on the System Settings > Login Items (Allow in the background). But the machine that already has installed the older app without AssociatedBundleIdentifiers still shows Developer ID due to the cached state. And it is commemted at https://developer.apple.com/forums/thread/713493. It can be updated by resetting command and then restarting the system, but doing it on my users' machines seems inappropriate in many ways. My question: So, is there any way that I can make the change(Developer ID -> App name) without resetting and restarting by any chance?

Obviously macOS allows to leave the password field blank so users can set the blank password. But in this case LAContext evaluatePolicy never allow authentication with empty password unlike System Settings(System Preferences). And canEvaluatePolicy produces true on macOS Catalina and BigSur. (while macOS Ventura returns false with "Passcode is not set." NSError) I tested with Intel macOS 11.7 BigSur and M1 macOS 13 Ventura, they work differently but they both failed to authenticate. The detail is as follows: [Intel / macOS 11.7 BigSur] & [Intel / macOS 10.15.7 Catalina] When evaluatePolicy called, the password window popped up. If I just click 'OK' button, the password window closed and popped up again right away. And clicking 'OK' again produces an error: (ACMContextVerifyPolicyEx returned 0, still requesting 1:1, 3:1, 15:1 (on context 9c1ee373)) And canEvaluatePolicy with LAPolicyDeviceOwnerAuthentication returns true on these environments.. [M1 / macOS 13 Ventura] When evaluatePolicy called, the password window doesn't pop up with an error: (passcode is not set.) Is this a bug or is there any way that I can figure out this case?

My app contains a daemon and an agent. So once it is downloaded, my deleloper ID shows on System Settings>General>Login Items (Allow in the Background). but even after uninstalling the app, my developer ID still on the list so it can be turned off anyway.(It is understandable.) When I turn off background item(my developer ID) and reinstall the app, the background item turned on automatically but an agent from my app failed to initialize after reinstallation. On the other hand, the daemon from my app works properly. I'm concerned that if this happen our users will have no idea why the app or the agent doesn't work even though the background item shows 'on' status. I summarized the steps and the error messages below. It can be reproduced on Ventura beta 10&11. Install the app A Background Item is added with my developer ID Uninstall the app My app's background item is still in the Login Items section Turn off my app's background item. Reinstall my app. My app's background item turned on after the installation. An agent in my app is expected to load but it did not show up. Error messages found from launchd.log are as follows: 2022-10-06 11:19:06.110655 (gui/501/com...**** [32250]) : Service could not initialize: Untrusted spawn was denied for /Library/LaunchAgents/com.ahnlab.v3mac.v3tray.plist, error 0xa1 - Service cannot be launched because of BTM policy 2022-10-06 11:19:06.110667 (gui/501/com...**** [32250]) : initialization failure: 22A5365d: xpcproxy + 21413 [422][59A833C0-060A-3ADE-A0C2-74CD09766F1D]: 0xa1 2022-10-06 11:19:06.110669 (gui/501/com...**** [32250]) : Untrusted service was denied launch by BTM. Removing. com...**** is my agent in /Library/LaunchaAgents