Re: Using defaults command to modify Info.plist changes permissions
Re: Using defaults command to modify Info.plist changes permissions
- Subject: Re: Using defaults command to modify Info.plist changes permissions
- From: "email@hidden" <email@hidden>
- Date: Tue, 15 Sep 2009 09:14:20 +0100
On 15 Sep 2009, at 01:43, Chris Suter wrote: Hi Jonathan,
On Tue, Sep 15, 2009 at 7:52 AM, email@hidden <email@hidden> wrote:
One of build phase script includes the perl variant of the following terminal command to inject a build number into my info.plist
defaults write /Users/Shared/Release/MyApp.app/contents/Info MyBuildNumber 123
Is it by design that the defaults command changes the access permissions to 600 (ie: no access for anyone but the owner)?
defaults (1) doesn't mention this side effect. running on 10.6.
The effect of this is to kill the app for users who are not the owner (at launch the info.plist cannot be read, hence no principal class, hence no launch).
Try using /usr/libexec/PlistBuddy. Using the defaults tool to modify plists is deprecated I believe.
Thanks for the pointer. PlistBuddy is new to me and looks like the tool of choice for this sort of thing. It leaves the permissions unaltered.
Jonathan Mitchell
Developer
|
_______________________________________________
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