OS update info within sysdiagnose is relatively helpful as it stands right now, but with the addition of Machine Learning updates via Global Settings, diagnosing what the device is thinking becomes a little bit more difficult. The SoftwareUpdateSubscriber channel gives some good info, but oftentimes it's not too insightful when an issue is happening. Let's say a device leveraging ML Global Settings isn't updating, and it's been about two weeks since a new applicable minor OS version dropped. The sysdiagnose says that it has the Global Settings in place, so it knows it needs to do the update this way. SoftwareUpdateSubscriber doesn't seem to report any error. So, what else could be the problem? Where can we look?
This makes things difficult to troubleshoot for those of us who are self-help focused, especially me, being in an MDM vendor support team. The process is no fault of anyone in particular, but sometimes a resolution is needed asap, and submitting feedback isn't meant for immediate assistance.
So, rounding everything out, I'd love to be able to see absolutely everything that updates on devices are thinking, ideally in a 'as organized as it can be' way, to help aid self-help resolutions. Related FB: FB18106259
Reading through the filed Feedback in question, I see the core issue you're getting at - which is namely: not all errors that are surfaced through the status report for software update issues are necessarily understandable or actionable by a device management vendor or the end user of a device management product.
As designed, the functionality intends to surface all errors, regardless of what they are, if one was triggered during the process.
We do make an attempt at trying to make them understandable and actionable, but there's always the possibility that a new unaccounted for failure scenario doesn't exactly have clear messaging.
Since your original Feedback was filed, multiple additional clarified responses were added which should have at least covered the example you provided in the Feedback.
If you're still seeing this particular example in OS 27, I would ask that you re-file a new Feedback during this WWDC beta cycle with a sysdiagnose collected from the device in question (or, as you did before, screenshots / copies of the messages in question - but with the additional full context of what OS version the device in question is currently running).
On top of that, if you have other examples of similar strings that are opaque in nature and not seemingly actionable - we would ask that you provide concrete examples of each one that you're seeing, again with the context of the OS it's being presented on.
Thank you for your feedback!
