InstallEnterpriseApplication MDM command will sometimes fail due to storedownloadd crash

Originator:codroid
Number:rdar://47038002 Date Originated:January 3 2019, 5:09 PM
Status:Open Resolved:
Product:macOS Product Version:10.14.1 (18B2084)
Classification:Crash/Hang/Data Loss Reproducible:Sometimes
 
== Summary

The InstallEnterpriseApplication MDM command will sometimes fail due to a crash in the storedownloadd process.

== Steps to Reproduce

Behavior is inconsistent and I have not found a way to reproduce it reliably yet. Steps to cause a chance of failure:

1. Enroll a device in MDM, either via DEP or UAMDM (configuration profile).
2. Issue a valid InstallEnterpriseApplication command to the enrolled device.
3. Issue a push notification or let the device check in to MDM to receive the command.

== Expected Results

The command is acknowledged, and the package gets downloaded and installed.

== Actual Results

Some percentage of the time, the package will not get downloaded or installed, despite the MDM command being acknowledged.

== Version/Build

macOS Mojave 10.14.1 (18B2084)

== Configuration

MacBookAir8,1

== Notes

Over the last few months, in a fleet of macOS devices with various hardware specs and OS versions, we have seen an increasing number of incidents of failed package installation via MDM. The package being installed is always the same and is smaller than the InstallApplication manifest hash chunk size. Until recently, this package had been successfully downloading and installing on devices via the InstallApplication MDM command consistently for over a year with no issue, aside from the occasional inevitable loss of internet connectivity.

It is possible some of the incidents we've seen result from an InstallApplication command, but this report details one which resulted from InstallEnterpriseApplication.

Description of incident:

On January 3, 2019, a new 13" MacBook Air enrolled in MDM through DEP. After successful enrollment, an InstallEnterpriseApplication MDM command was immediately issued for the device and a push notification was sent to the device. The command was acknowledged, but after half an hour the package had still not been installed. The failure was eventually detected and a second, similar command was automatically enqueued. This command was also acknowledged as soon as the device went online, but the package failed to install again. I started looking at system logs; meanwhile, a third command was enqueued. The device received this command and quickly succeeded at installing the package.

These two log lines show in system.log. The log timestamps are each within one second of the corresponding (failed) MDM command acknowledgement. The attachments in this issue (storedownloadd crash logs) correspond to these times as well.

Jan  3 09:46:13 [...] com.apple.xpc.launchd[1] (com.apple.storedownloadd.daemon[488]): Service exited due to SIGILL | sent by exc handler[488]
...
Jan  3 11:02:04 [...] com.apple.xpc.launchd[1] (com.apple.storedownloadd.daemon[851]): Service exited due to SIGILL | sent by exc handler[851]

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!