Permissions problems for compiled application
Permissions problems for compiled application
- Subject: Permissions problems for compiled application
- From: Keith Blount <email@hidden>
- Date: Fri, 23 Apr 2010 02:08:00 -0700 (PDT)
Hello,
When my program is compiled in Xcode, it seems to experience certain permissions issues, as follows:
• It works fine on an admin / main user account.
• If I take it to another account on my computer, it won't launch, with an error about a missing info.plist. Checking the permissions of the info.plist inside the application, its permissions are set to "No access" for "everyone", "Read & Write" for "me" and that's it - so no wonder the other account cannot open the app.
• Other resources inside the application bundle have the same problem as the info.plist file (the same permissions - "No access" for "everyone"). As I have certain resources inside the app that should get copied to the user's account (such as a Tutorial file) if the user requests it, this is a major problem (it means that users outside of the main admin account cannot access the tutorial, for instance).
I've checked the permissions on the files inside the Xcode project, and even tried applying read/write permissions to the whole Xcode project folder and contents, so the original files are fine. But as soon as it's compiled, the permissions on the resources placed inside the application bundle are changed so that many are "No access" to other users.
I've also checked my Xcode Install Permissions and Alternate (surely Alternative? :) ) Install Permissions, and these are set correctly to "u+w,go-w,a+rX". I searched Google and the archives, and from what I found there it seems these permissions have no effect on resources anyway, though. One reply to the only similar question posted I could find (and unfortunately lists.apple.com is reporting too many SQL connections to search right now, so I can't find the answer I'm referring to right now), said that the only way to apply permissions to resources during build was to create a build phase script, but the poster described this as a "hack" so this doesn't sound as though it should be necessary.
Has anybody else had similar permissions problems? At the moment this means that my app can only be used from the main user account. Obviously I can fix this manually post-build, but there must be a better solution, or perhaps something is wrong with my set-up?
Many thanks in advance and all the best,
Keith
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden