They're probably referring to the certificate verification that happens when you open any notarized application. Unless something changed recently, the system phones home to ensure its certificate wasn't revoked.
It doesn't do that on every app launch; there's a cache. It does it on the first launch of a binary from a new team.
(So multiple binaries with the same team don't check either.)
And I'd expect all logging is disabled on the CDN.
Re:M4 MacBook Pro
by FireBeyond on Thursday October 31, 2024 @12:39AM
(#42003553)
I have no reason to expect that it is.
It does kind of suck if the binary is frequently updated, big and you have a slow internet connection. So some program which normally takes seconds to open can take 20 or more seconds to open after an update. Or if you don't use that program frequently, you always get a very slow start of a program.
> Even if I have analytics disabled?
Yeah because what’s being sent is not analytics but related to notarizarion, verifying the app’s integrity (aka is it signed by a certificate known to Apple?)
This came to light a few years ago when the server went down and launching apps became impossible to slow…
Genuinely asking: are there any specifics on this? I understand that blocking at the firewall level is an option, but I recall someone here mentioning an issue where certain local machine rules don’t work effectively. I believe this is the issue [1]. Has it been “fixed”?
[1] https://appleinsider.com/articles/21/01/14/apple-drops-exclu...