NSFileManager file copy gives misleading error when violating sandbox

Originator:lithium3141
Number:rdar://16561560 Date Originated:08-Apr-2014 07:58 PM
Status:Open Resolved:
Product:OS X SDK Product Version:OS X 10.9.2 (13C64)
Classification:Other Bug Reproducible:Always
 
Summary:
When attempting to use NSFileManager to copy a file from an unsandboxed location into a sandboxed app's container, I encounter an error (as expected). However, the error misleadingly claims that my app cannot access its own container, rather than being unable to access the unsandboxed file.

Steps to Reproduce:
1. Create a new app.
2. Construct a path to a file that exists outside the app's sandbox.
3. Use NSFileManager to copy that file into the app's sandbox.

Expected Results:
I get an error that indicates the app is unable to access the unsandboxed file (since it has no security exception to do so).

Actual Results:
I get an error that claims the app is unable to access its own sandbox container.

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!