Jay Gamel wrote:
What I would like to know is why apple cannot identify the offending app and include it in the notice. Obviously, the warnings are issued on a specific instance related to a specific app. I am not a programmer so I don't understand what prevents the app ID from being recorded and reported.
This entire new interface, and the notifications, are all part of Apple's effort to do exactly that. Apple, or perhaps NextStep?, didn't anticipate this back in 1989. Back when Apple purchased NextStep, they had no interest in this kind of issue. They were only interested in avoiding bankruptcy. To do that, they had to run classic MacOS apps. Nobody cared one whit about launchdaemons or login items back then. In technical, programmers terms, this is called "technical debt". If the only way to avoid your death is an expensive medical procedure, you'll take out a loan, regardless of the terms, to pay for it.
But then, something funny happened on the way to the funeral. Steve Jobs was like those doctors on the TV shows. He resuscitated the patient multiple times. And then he pulled a Jed Clampett, striking oil while shootin' at some food.
And now Apple is paying off that debt. Or rather, we are paying for it. 😄 Apple introduced an entirely new way to manage these items that works exactly as you describe. The problem is that 30 year history of legacy apps. It is expected that when people freak out over "Google LLC" and "Elmer Hasenpfeffer" on their computer and disable those apps. So, in order to survive, any developer relying on that old style of programming is going to have to adopt the new APIs. The plan is brutal, but effective.