How to Identify a "Phantom" Write Operation
How to Identify a "Phantom" Write Operation
- Subject: How to Identify a "Phantom" Write Operation
- From: douglas welton <email@hidden>
- Date: Tue, 04 Sep 2012 18:17:14 -0400
Hi All,
I'm trying to get an app approved for the Mac App Store. The reviewer says that my app is writing to a certain user-selected file without the user's permission. I don't see any evidence of writing to this file, but my knowledge of the file system internals may be insufficient to help me in this situation.
Here's what I'm doing:
1) In my sandboxed application, the user selects a movie file from an open panel.
2) I copy the selected file to the ~/Library/Caches folder within my sand box container (using NSFileManager's -movieItemAtURL: method).
3) I open the cached version of the file (using QTKit) and let the user manipulate the movie using various QuickTime functions.
4) The user can either export a new QuickTime movie (featuring their changes) to a user -specified locations or exit the application (saving their manipulations but not making any changes to the original source)
5) When the user exits the application, the cached file is removed
When I examine the finder info for the user-selected file, the modification date never changes and the size remains exactly the same. I have also run the application with Instruments using the "Reads/Writes" instrument to check file activity. What I see on the Instruments' Event List is that the path for the user-selected file shows only read operations, no writes. The only write operations in the Event List belong to the cached version of the source file (and various application .plist)
Contrary to what I am seeing in Instruments, the reviewer obviously has some tool that indicates that the file is being written to.
My question: Is there another way to check for writes to the user-selected source file?
Thanks,
douglas
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden