Under Ventura we are noticing that our software "service" is displaying under Apple Settings the "person's name" associated with the Apple Account rather than labeling the service using the name of "the service". Obviously confusing.
Does anyone have a suggestion how to get a service to grab and use the service name from some plist entry in the Launch Daemon plist file?
Any clues would be very welcome.
Thanks.
TCC wants to be able to map your launchd job’s name to some sort of user-visible app. If your product includes an app, add its bundle ID to the AssociatedBundleIdentifiers property in your launchd property list. See launchd.plist man page for the details.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Hello Quinn "The Eskimo". Thank you sooooo much for this response. I will share it with my dev team leader with hopes it sparks an idea/solution to this issue. Much appreciated. Peace.
Hello Again,
We looked over the data supplied (thank you), but so far it is not the resolve we seek. Our issue being that the "service" being loaded at login (login items) has the wrong name. It is showing my proper name instead of the service name "ripengine" which is what it needs to be. We believe it might be due to how we signed the our certificate. This has only become an issue under Ventura which seems to be taking the service name differently.
My question now would be can we resign the certificate putting the service name in the place where Ventura is drawing my proper name? Is that even possible?
I hope this is making sense to someone and that you have advice for us. Much appreciated.
The more info you can share with how Ventura is handling things now will be greatly appreciated.
See image attached.
Clearly your product includes a launchd daemon. Does it include any other components, ones that have are user facing, like an app?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Hi Quinn,
We are making some progress. We now have our product icon appearing next to the service name so that is good, but we still lack the proper "service name". It still shows my name as the "common name" under Login Items.
Yes, we have an application with a full UI. This service (ripengine) runs to produce prints. We do have more than one software that we sign so now we are thinking this way.
Is it as simple as we change the "common name" when making a NEW signing document? In this case we either use the name of the service "ripengine" or the company name of "Bluironic" other than may proper name? Will the document be approved if handled this way? Will this be the name that appears under the Login items?
We find in our systems we do not have a LaunchID Daemon in the folder you suggested (Library/LaunchDaemons). We see these items for other products we use, but ours is missing. Is this the issue?
Much appreciated
when making a NEW signing document?
I don’t know what you mean by “signing document”. That’s not a term we use in any of our code signing documentation.
With regards you main issue, does this issue reproduce if a) adopt AssociatedBundleIdentifiers, and b) install that new version of your product on a machine that’s never seen your product before?
It’s possible that AssociatedBundleIdentifiers fixes your issue and you’re just dealing with a caching issue. By testing on a ‘clean’ machine, you’ll be able to rule out (or in, I guess) that possibility.
I usually do this sort of testing on a VM, where I can revert to a clean snapshot between each test.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
