Ineligible files in iCloud Drive lost without warning

Originator:wjwickham
Number:rdar://29425901 Date Originated:29 November 2016
Status:Open Resolved:
Product:macOS Product Version:10.12.1 (16B2555)
Classification:Crash/Hang/Data Loss Reproducible:Always
 
Summary:
Files that are "ineligible" for iCloud Drive storage (e.g. image files in an Xcode Asset Catalog) are lost without warning.

Steps to Reproduce:
1. Enable "Desktop & Documents Folders" in iCloud Drive preferences
2. Create an Xcode project on the Desktop
3. Add assets to the project's asset catalog
4. When the machine's local disk space gets low, the system will "purge" the project folder from local storage and make it available to download from iCloud Drive when needed.
5. Download the project from iCloud Drive to local storage and open in Xcode; the asset catalog will be empty.

Expected Results:
Users should be able to store files of any kind in iCloud Drive with the confidence that they won't be corrupted or lost by the service — especially when this is the default behavior of the system.

Alternatively, the system must warn users when ineligible files are added to iCloud Drive, informing them that when the system reclaims local storage space, ineligible files will be lost.

Actual Results:
iCloud Drive does not warn the user of ineligible files, allowing files to be lost entirely when local disk space is reclaimed.

Specifically, an Xcode asset catalog can be downloaded from iCloud Drive, but each "ineligible" file contained in the catalog has been renamed ".filename.extension.icloud" and can no longer be opened.

Version:
macOS Sierra 10.12.1 (16B2555)

Notes:
These files couldn't be restored on iCloud.com. Settings > Restore Files completely failed to load with the error "There was a problem loading restorable files."

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!