Legacy LaunchAgents installed via PKG

I was wondering the same thing as well. We see this where both our daemon and agent in the "Allow in Background" list in the Ventura System Settings show up as our developer name rather than the application name from 'AssociatedBundleIdentifiers' in the plist files. And, if we register AND open this app before the LaunchAgent and LaunchDaemon are loaded then it works but this is tricky to implement in an installer package.

We're running into similar problems with the app name not being shown in the system settings. Please let us know if you find a solution. How do you call LSRegisterUrl in the postinstall script? Do you have a dedicated binary for that?

Were you able to solve your problem? Facing the same issue.

I would also like to know if there is a solution. We have the same issue.

Our product is rather complex with an application, a daemon, an agent plus some other components (like an authorization plugin) so it is just simpler to install via a package (built with productbuild --distribution). We have added the AssociatedBundleIdentifiers key to the launchd plist for both the daemon and agent but they still show under our developer name and not the application in System Settings after installing. It is only after running sfltool resetbtm and restarting that the daemon and agent show with the application name.

I have tried using /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister to register the application in its postinstall script (which executes before the daemon or agent gets installed) but that didn't help.

Someone opened a DTS tech support incident about this. I think I found a reasonable workaround but I need to do further research before talking about it publicly. I’ve made a note to update this thread once that’s done.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

We have a similar problem. After adding the AssociatedBundleIdentifiers to the LaunchDaemons' plist files they are at least labeled with the developer name instead as before with something completely unrelated. Then we tried to start the app in the postinstall before loading the LaunchDaemons. Now one item has the name of the app, the other one has still the developer name. It seems the notification banners appear when starting the app, not when loading the LaunchDaemons. Is that possible?

@eskimo : Did you get anywhere with your research? I have just run into this issue too.

Did you get anywhere with your research?

Not really. My ‘cunning plan’ was to explicitly register the ‘parent’ app with Launch Services in the installer package’s post-install script before copying the agent’s launchd property list to /Library/LaunchDaemons. This helps in some situations but the developer I was working with still managed to hit cases where it fails.

At this point I’m out of ideas and my advice is:

1. Make sure the problem reproduces on the latest system running on a ‘fresh’ machine. That is, one that’s never seen your product before. I generally do this sort of testing in a VM, restoring to a fresh snapshot between each test.

2. If so, file a bug, including a copy of your product and a sysdiagnose taken shortly after reproducing the problem.

If you do file a bug, please post your bug number here, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"