I think I asked this before, but wasn’t able to solve the problem. Under Ventura the login items show for all other apps the app name or the company name:
As a private developer, you can not change your developer’s name if I remember correctly unless you have an official document or switch to an organisation account.
It seems to me that Apple is pulling this information from the code signature.
IIRC and this was some time ago, to register a company with Apple, you need to have a certain kind of company and send the information to Apple and wait for them to “verify” it and allow you to use your company name.
We had to register Ohanaware as a Limited Company for Apple to accept the company name Ohanaware, otherwise they would just use my name, which I didn’t want as everywhere else we use the name Ohanaware.
I want to port my apps to the new logic but I am not quite sure how to do that. I don’t want my apps to appear under the “Allow in the Background” section but rather in the “Open at Login” section.
These are very different things:
Open at Login shows a list of login items, per the legacy kLSSharedFileListSessionLoginItems API. These items are always launched at login, and are intended to be under the control of the user.
Allow in the Background has different semantics. This is an allowlist. It doesn’t show what programs will be launched at login, it shows what programs are allowed to be launched at login [1].
You can see this with the SMLoginItemSetEnabled API:
Enable your Service Management login item by calling SMLoginItemSetEnabled with true.
The item shows up in the Settings list.
Back in your app, disable your login item by calling SMLoginItemSetEnabled with false.
My understanding of what Quinn says is two things.
Legacy means of launch on login, works as expected.
Newer API, doesn’t mean that an app or service will launch on login, it means it has permission to do so.
As for what determines what gets displayed, AFAIK the specifics are not public information. You could burn a DTS if you want and ask Apple, what’s going on here. DTS are great, but don’t always expect an answer as they may NOT be able to give you answer if they’re not allowed to do so, you know for security and privacy, and privacy of the security.
Addendum: I also understand from point 2, that control over LoL is handled from within your application. However this means that the customer has to check and make sure that it is activated in your application, and has to check System Preferences Settings to make sure it has permission.
Burning a DTS sounds like a good idea. I did one 2 years ago. While I didn’t get an answer (I’m just a peon) I got the showstopper bug I had fixed in a timely manner.
I’ll also contact the developers I saw in the Twitter pics and make some Feedback thingies.
You get two a year and they don’t roll over, so use 'em.
Quinn is one of the DTS engineers, and he’s often on the ADF, helping out where he can. He’s also on Twitter, but asks not to talk about work there, yet we still talk about things Apple and such, I just don’t bug him with questions on Twitter.