Lion problem report and fix
Shao Sean
shaosean at wehostmacs.com
Fri Jul 22 01:22:30 EDT 2011
For those that are submitting Rev apps to the Mac App store, this
might be useful to you (and could also be good idea to follow for non-
Mac App store downloads as well)..
File-System Usage Requirements for the Mac App Store
To promote a more consistent user experience, applications submitted
to the Mac App Store must follow certain rules about where they write
files. Users can be confused when applications cause unexpected side
effects on the file system (for example, storing databases in the
user’s Documents folder, storing files in the user’s Library folder
that are not recognizably associated with your application, storing
user data in the user’s Library folder, and so on).
Your application must adhere to the following requirements:
• You may use Apple frameworks such as User Defaults, Calendar Store,
and Address Book that implicitly write to files in specific locations,
including locations is not allowed to access directly.
• Your application may write to temporary paths that you acquire using
the appropriate Apple programming interfaces.
• Your application may write to the following directories:
• ~/Library/Application Support/<app-identifier>
• ~/Library/<app-identifier>
• ~/Library/Caches/<app-identifier>
where <app-identifier> is your application's bundle identifier, its
name, or your company’s name. This must exactly match what is in
iTunes Connect for the application.
Always use Apple programming interfaces such as the
URLsForDirectory:inDomains: function to locate these paths rather than
hardcoding them. For more information, see File System Programming
Guide.
• If your application manages libraries of pictures, music, or movies,
the application may also write to the following directories:
• ~/Pictures/<app-identifier>
• ~/Music/<app-identifier>
• ~/Movies/<app-identifier>
• If the user explicitly chooses to save data in an alternate location
(using a Save As dialog), your application may write to the chosen
location.
More information about the use-livecode
mailing list