• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Opening a file read-only?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Opening a file read-only?


  • Subject: Re: Opening a file read-only?
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 20 Jul 2011 08:56:12 -0700

On Jul 19, 2011, at 6:55 PM, Graham Cox wrote:

> Because we just got rejected on the App Store for opening a file with read/write access in a place that's not allowed. I've checked the code that we're not writing or creating files to these locations - we're not - so the only other possibility is this.

Try running fs_usage while your app is running, and you’ll be able to see what files it opens and in which modes.
(Or there’s probably an Instrument for that now?)

That said, I would be very surprised if -initWithContentsOfMappedFile: opened the file writeable.

—Jens_______________________________________________

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

References: 
 >Opening a file read-only? (From: Graham Cox <email@hidden>)
 >Re: Opening a file read-only? (From: Greg Parker <email@hidden>)
 >Re: Opening a file read-only? (From: Graham Cox <email@hidden>)

  • Prev by Date: Re: NSBeep() blocks for some users
  • Next by Date: Re: NSBeep() blocks for some users
  • Previous by thread: Re: Opening a file read-only?
  • Next by thread: NSBeep() blocks for some users
  • Index(es):
    • Date
    • Thread