I did file a bug with FB12140694 I tried "realistic user scenarios" recently and found out that the app's icon is updated perfectly but the app's name is still my developer ID. While this is really a trivial matter, I filed bug report to briefly let you know and to manage my own tasks as well. I attached an old app, a new one and the output from [ sfltool dumpbtm ] for reference. macOS 13.3.1(22E261) Installed my earlier App. My developer ID showed up with a default gray icon on Login Items > Background Items Updated the app to new one that add AssociatedBundleIdentifiers in plists of my daemon and the agent. Upadate finished. My developer ID wasn't changed to my app's name but the icon has changed properly. P.S. When I installed my new app on clean macOS, the app's name and icon showed up perfectly on Login Items > Background Items.

Yes, I referred sfltool. I just want to make sure whether there is any other way to update login item without doing $ sfltool resetbtm + restart the system.

Thanks to Eskimo, this issue was automatically solved by adding AssociatedBundleIdentifiers key as described in https://developer.apple.com/documentation/servicemanagement/updating_helper_executables_from_earlier_versions_of_macos?language=objc Sorry for the late reply. I just closed the bug reports(FB11654595, FB11696339). The problem was the other app that is under the same organization name without AssociatedBundleIdentifiers. Thank you.

Thanks for your comment. I totally agree with that macOS 13 behaviour seems more reasonable. Now, I got two questions: Is there any possibility that having an update in the future for canEvaluatePolicy and evaluatePolicy or macOS so they can work the same on macOS 13 and less than macOS 13? Unlike evaluatePolicy, with SFAuthorizationView and System Settings(System Preferences), they can just pass the password window with 'OK' button without typing password. Is the different behaviour of evaluatePolicy intended?

The bug report number is FB11696339. Please let me know if there's any update on this issue. And thank you for the information about SMAppService API. The document contains more information that I didn't know. Thanks!

Should I consider this matter as a bug or am I missing something?