iOS iTunes file sharing needs atomic copies to make it safer and with better UX

Originator:felipekellermann
Number:rdar://11777005 Date Originated:29-Jun-2012 11:57 AM
Status:Open Resolved:
Product:iPhone/iPod touch Product Version:5.1.1
Classification:Enhancement Reproducible:Always
 
29-Jun-2012 11:57 AM Felipe Kellermann:
Summary:
The iTunes file sharing feature copies the content in a non-atomic way and there is no API currently in the iOS to detect if iTunes is still copying the content or the content is already complete. This makes the feature of copying content a unsafe and affects the user experience (that normally is required to take some action in the application to "read" the content).

Steps to Reproduce:
1. Create an app that supports iTunes file sharing feature.
2. Copy a large content (for instance, a 1GB file).
3. The app sees the file but there's no way to check if the copy (sync) already finished.

Expected Results:
A method to check whether the copy (sync) already finished or not. Or even better: make the copy (sync) be an atomic operation using a temporary name and a move (atomic). For instance, user copying (syncing) fuu.bar would be fuu.bar.copying and then fuu.bar (atomically).

Actual Results:
No atomic copy (sync), no way to check whether the copy (sync) finished or not.

Regression:

Notes:

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!