Posts

Post not yet marked as solved
1 Replies
131 Views
Is software update error 41 the equivalent of a theoretical “DownloadAlreadyPresent” UpdateResults item? When MDM sends ScheduleOSUpdate w/ DownloadOnly to a device that had previously downloaded the update by itself (device has automatic update downloads enabled), it returns: The operation couldn't be completed. (com.apple.softwareupdateservices.errors error 41 Should MDM treat that as a success and move on to InstallASAP?
Posted
by Elektrik.
Last updated
.
Post not yet marked as solved
0 Replies
167 Views
We're looking into enabling the installation of iOS apps on Mac computers with Apple silicon as introduced in macOS 11.3, but we've discovered a bit of a challenge related to the metadata available to know when this is appropriate to allow.  Our understanding is that iOS/iPadOS apps (not Universal Apps) on the App Store can be in one of three states, based on the "Manage Your App" section of that article: Developer does nothing and app is listed by default. That results in "not verified for…", like this:  Developer explicitly opts-in, which removes the "not verified for…" text, like this:  Developer explicitly opts-out, which hides the app entirely from the iPhone and iPad Apps section of the purchase history in the App Store. For example, search for "Chipotle". Is there metadata available in the VPP/Apps and Books API that maps to these states? There is guidance on identifying universal apps, but this is different. We'd like to present the same sort of view as the App Store to our customers when they're scoping iOS/iPadOS apps to allow for inclusion of Mac computers with Apple silicon. We've also filed this request in FB9957387. Thanks!
Posted
by Elektrik.
Last updated
.