I am also noticing this same crash
An Apple engineer has provided me the following explanation:
The app could not communicate with a helper application (i.e. the photo library). The most common reason that
assetsdmight crash is because the foreground app is using a lot of memory (or allocating memory very quickly), and the system decides to terminate
assetsdto alleviate some of that memory pressure.
To prevent these errors, you should make sure that your app is not triggering a high memory pressure situation.
This should only be a temporary issue. In other words, if you tried to submit the same request later, it may work (assuming that any high memory pressure situation has been resolved). So, I recommend that you queue up requests that fail and try to submit them later, and inform your user of this in some way, so that they know the save has not gone through yet.
This same issue can also create an error with the code
NSCocoaErrorDomainand the description:
Couldn’t communicate with a helper application.