Re: Patching Watchkit App's info.plist at build time.
Re: Patching Watchkit App's info.plist at build time.
- Subject: Re: Patching Watchkit App's info.plist at build time.
- From: Alexander von Below <email@hidden>
- Date: Mon, 13 Jul 2015 20:38:46 +0200
I have tried, and failed, to to this. The problem was, IIRC, that the App target does not have a pre-build shell script action.
Let me know if you come up with something
Alex
> Am 13.07.2015 um 20:21 schrieb Owen Hartnett <email@hidden>:
>
> My build script has the pleasant feature of changing CFBundleVersion to the current Subversion revision number during a build phase.
>
> Here's the line of script code:
>
> /usr/libexec/PlistBuddy -c "Set :CFBundleVersion `svnversion -n`" ${TARGET_BUILD_DIR}/${INFOPLIST_PATH}
>
> Now that I've added a Watch App and Watch Extension, Xcode whinges that the Watch App CFBundleVersion must match the iOS app's CFBundleVersion. I'm looking for a way to patch the Watch App plist at build time (in the above manner). It gets built before the iOS app, and it doesn't have build phases, but the extension does.
>
> I haven't been able to find this plist in the finished product, having peeked in all the packages. I can get it to build, by making both CFBundleVersions zero, but what fun is that? Is there a way to do it in building the extension, or at iOS app building time?
>
> -Owen
> _______________________________________________
> 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
_______________________________________________
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