We tried installing ipa file in m1 Mac ( tried both mac11 and mac12 silicon mac), but it failed with error informing - Error Domain=ASDErrorDomain Code=660 "Could not create PKProduct". Attaching the log and plist details ipa-failure-devicelog.txt the plist - install application command

We are testing the new InstallAction option InstallForceRestart (https://developer.apple.com/documentation/devicemanagement/scheduleosupdatecommand/command/updatesitem) on macOS 11 devices per the documentation and we are getting an error that it is an unsupported action for this Product Key. If we use the InstallAction of Default instead with the same Product Key the update is fine. Plist with error is <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "..."> <plist version="1.0"> <dict> <key>CommandUUID</key> <string>0b17230e-7096-4972-be30-1f23fb8c4d6d</string> <key>ErrorChain</key> <array> <dict> <key>ErrorCode</key> <integer>12008</integer> <key>ErrorDomain</key> <string>MCMDMErrorDomain</string> <key>LocalizedDescription</key> <string>Unsupported InstallAction for this ProductKey</string> </dict> </array> <key>Status</key> <string>Error</string> <key>UDID</key> <string>54354E4B-F56B-5D62-83C9-990342AD570B</string> <key>UpdateResults</key> <array> <dict> <key>ErrorChain</key> <array> <dict> <key>ErrorCode</key> <integer>12008</integer> <key>ErrorDomain</key> <string>MCMDMErrorDomain</string> <key>LocalizedDescription</key> <string>Unsupported InstallAction for this ProductKey</string> </dict> </array> <key>InstallAction</key> <string>Error</string> <key>ProductKey</key> <string>MACOS11.1</string> <key>Status</key> <string>InstallFailed</string> </dict> </array> </dict> </plist> Anyone else seeing this error or have people been able to get the InstallForceRestart option to work?

When we push Desktop/Wallpaper configuration to UserEnrolled Mac devices, we get an acknowledgment. But device is not reporting the config in the installed Profile list report.  Issue is seen with only Mac UserEnrolled device ( Tested with 10.15 , 11 os version). As per apple doc this is supported in UserEnrolled devices as well

Hi, can you please confirm if Apple supports - is provisioning profile is support on m1 Mac ? any specific m1 Mac version onwards? if the iOS app is supported on m1 Mac, then the respective iOS provisioning profile would work on m1 Mac as well?

Regarding allowWallpaperModification setting in https://developer.apple.com/documentation/devicemanagement/restrictions, 1) Is this setting supposed to work on supervised macOS device only or on non-supervised macOS device as well? 2) From our testing, we observed that for the setting change to be effective on the device, device restart is required. Is this expected?

Hi, in ios14.5 we have new restriction "forceWiFiToAllowedNetworksOnly". This limits device to only join Wi-Fi networks set-up via configuration profile. If there is no valid wifi payload installed then this would stop communication with MDM server right? If so, is there any recommendation on how to handle this or whether there are any constraints to check and not send this recommendation if so?

https://developer.apple.com/documentation/devicemanagement/airplay?changes=latest_minor AllowList is newly added. older field Whitelist - doc says "Use AllowList instead. " , Is 'whitlist' deprecated , can admin still use it in any os version. 2. AllowList - is it alpha numeric in that format xx:xx:xx:xx:xx:xx

As per the Web content filter payload documentation at https://developer.apple.com/business/documentation/Configuration-Profile-Reference.pdf page#106, it allows multiple payloads. But as per the latest document https://developer.apple.com/documentation/devicemanagement/webcontentfilter?changes=latest_major, it does not allow multiple payloads. Can we get answers for the below queries? What is the current expected behaviour WRT to multi /single payloads for web content payload on iOS and macOS? If the functionality is changed to single payload from multiple payloads, from which iOS and macOS versions is this change effective? If multiple payloads were earlier accepted and the device is updated to a version where only single payload is allowed, how does device prioritise/ merge the payloads during update?

On Apple silicon Mac running 11.4 when device lock is performed through MDM, the device is going to activation mode. Instead it should get locked. There were a few blogs where the issue is talked about but nothing concrete from Apple documentation. Please direct us to the right documentation on Device lock support for Apple Silicon.

While issuing a device deviceLock command to intel based Monterey device, if PIN, message & phone number are set, message is displayed rightly, but nowhere phone number gets displayed on lock screen. Please point to documentation which describes the supportability of these fields.

We are trying out Account Driven User Enrollment feature. Device is expected to send the device info(plist) (snippet below) during User enrolment in new flow as part of profile download request. Device is sending with HTTP request content type as "application/x-www-form-urlencoded", because of this HTTP request content type, we are not able to read the body as stream of bytes and parse the xml. In comparison to usual device enrolment workflow device info gets posted with the http request content-type  as "application/pkcs7-signature" which has been working fine without any issues. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>LANGUAGE</key> <string>en-US</string> <key>PRODUCT</key> <string>iPhone10,2</string> <key>VERSION</key> <string>19A222</string> </dict> </plist> Can you please confirm if this is an issue from Apple side? Any suggestions around this?

In new Userenrollment flow (Account driven User enrollment), we are challenging the authentication by sending authentication URL which has a query parameter source=NATIVE as below : WWW-Authenticate: Bearer method="apple-as-web", url="https://ourauthserverdomain.com/ireg/index.html?source=NATIVE but when device makes the request to this url when it opens the webview it is ignoring query parameter sent from server (here, source=NATIVE).

This is in reference to the feedback ticket : https://feedbackassistant.apple.com/draft/57929340, we would like to know if there are any test enterprise websites that Apple can suggest to test passkeys declaration.

As per documentation at https://developer.apple.com/documentation/devicemanagement/dock/staticitem/tile-data, file-type is a required field and the possible values are 0, 1, 3. But in the file present on Mac device at ~/Library/preferences/com.apple.dock.plist, the values for file-type are 41, 40, 2, 1, 169. Can you please help with the valid possible values for the field file-type? And also please help with what each those values mean? Attached the dock preference file from Mac device. com.apple.dock.plist - https://developer.apple.com/forums/content/attachment/8f8e62a4-322b-45b1-a94d-643d8539589b

Is there any metadata in ios apps that can be used to determine if an iOS app can be installed on M1 device? https://affiliate.itunes.apple.com/resources/documentation/itunes-store-web-service-search-api/ - metadata returned by this search API does not have any indication of whether the iOS app is applicable for macOS 11 or not? Ex: curl -s 'https://itunes.apple.com/lookupid=281796108&amp;amp;country=RU&amp;amp;l ang=en' O/p of the API response is attached. O/P of API of App that is also applicable on M1 - https://developer.apple.com/forums/content/attachment/53aab414-e2bc-4f67-a5e7-b82df6b6bd89