Here's a strange one.
In my app I have a bunch of templates which are packaged documents
loaded directly from my app's resources. On my system and the vast
majority out there, they work fine. But a couple of users have
reported that they don't see them.
I've tracked down the issue to the check for a file package. On these
few systems, - (BOOL)isFilePackageAtPath:(NSString *)fullPath is
returning NO, so the package gets treated as a folder and has its
contents scanned (by NSDirectoryEnumerator) instead of being added to
the list of templates. Similarly, the Finder shows the package as a
folder not a file, so somewhere the package flag is getting blitzed.
Anyone got any idea how that can happen? The app is downloaded as a
zip file, unzipped and is simply drag-installed to /Applications (or
wherever). Does the package flag rely on the unzipper utility knowing
how to deal with it correctly? Maybe these few people used a different
unzip utility... </grasping at straws> Can permissions have a bearing
on this? The containing resources folder is read/write for the owner,
read for 'everyone' and has no group permissions set at all (7-0-5).
Then again, it works for the vast majority, so it can't really be that.
--Graham
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
