3 ms·
> Unfortunately, it is a client-side issue affecting both 11.0.1 and 11.1 clients. So there’s not much Apple can do to provide a fix. Seems rather unlikely to
by jmull 6y ago
> Unfortunately, it is a client-side issue affecting both 11.0.1 and 11.1 clients. So there’s not much Apple can do to provide a fix.
Seems rather unlikely to be true.
- random5634 6y agoAgreed. I wonder how they arrived at this conclusion.
- TobTobXX 6y agoI can't really interpret what "client side" means for a system update. What would be the "server side"? This would make sense, if you set up remote code execution for apple servers, but I could not imagine something horrible like that.
- jmull 6y agoIn this case, client means your mac running macOS — there will be a system update process running on your mac. The server is the the apple server the update process talks to to figure out what to download (and then to download it). (I haven’t looked at it but there are probably multiple mac processes, with their own set of relationships, and multiple Apple services involved, but for the purpose of this issue, you can think of the client side being anything running on your mac, and server side as anything running on an Apple server.)