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.
bluironic
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
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.
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?
Can we make as many signed docs as needed to be applied to each software product as needed or must we make a universal Code Signing doc?
Much appreciated