Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

how to get XCode to add build date & time to Info.plist file

Finally... after a couple years of watching and a month of participating, I have a chance to ask you guys a question of my own.

My boss doesn't trust me (or any process) to increment a build number, he also wants to have a build date & time baked into the app. I'd like to put this into the usual Info.plist file.

I found this related question:

Build information in iOS Application (date/time app was built)

and based on the answers there, I went into the Scheme Editor and added the script below to the "Post-Action" section of the Build phase:

infoplist="$BUILT_PRODUCTS_DIR/$INFOPLIST_PATH"
builddate=`date`
if [[ -n "$builddate" ]]; then
    defaults write "${infoplist%.plist}" BuildDate "${builddate}"
fi

In XCode, my Scheme Editor window looks like this:


(source: myke at maniac.deathstar.org)

Unfortunately, BuildDate never gets written into Info.plist.

Changing "${builddate}" to "$builddate" doesn't work either. I added this line to the script:

echo "build date is $builddate" > /tmp/result.txt

and the date appeared perfectly fine in the written out file. Writing strings into the Info.plist file from the above script works perfectly fine, annoyingly enough.

So, summed up, how to get the date to be added to the Info.plist file?

like image 897
Michael Dautermann Avatar asked Oct 30 '11 09:10

Michael Dautermann


People also ask

How do you declare a date variable in Swift?

Creating a Date and Time in Swift For this you can use DateComponents to specify the components and then Calendar to create the date. The Calendar gives the Date context.


2 Answers

Ahhhh, I should have spent another 30 minutes (on top of the 2 hours I had already wasted) and looked at the answers for this question before posting my own:

Insert Subversion revision number in Xcode

This post-action script does the trick and works for me:

infoplist="$BUILT_PRODUCTS_DIR/$INFOPLIST_PATH"
builddate=`date`
if [[ -n "$builddate" ]]; then
    # if BuildDateString doesn't exist, add it
    /usr/libexec/PlistBuddy -c "Add :BuildDateString string $builddate" "${infoplist}"
    # and if BuildDateString already existed, update it
    /usr/libexec/PlistBuddy -c "Set :BuildDateString $builddate" "${infoplist}"
fi

As you can see, it's doing a bit of a hack there (adding it if it doesn't exist; setting it right afterwards).

If anyone can suggest a solution using the "defaults write" method above (which I think might be better supported than "PlistBuddy"), I'd be thrilled to find out (and of course I'll accept and use that superior answer, too).

like image 64
Michael Dautermann Avatar answered Nov 05 '22 14:11

Michael Dautermann


The code in Michael's answer is incorrect or no longer up to date. The version below fixes an error in the set syntax and also supports build paths with spaces in them.

infoplist="$BUILT_PRODUCTS_DIR/$INFOPLIST_PATH"
builddate=`date`
if [[ -n "$builddate" ]]; then
    # if BuildDateString doesn't exist, add it
    /usr/libexec/PlistBuddy -c "Add :BuildDateString string $builddate" "${infoplist}"
    # and if BuildDateString already existed, update it
    /usr/libexec/PlistBuddy -c "Set :BuildDateString $builddate" "${infoplist}"
fi

Note: This change was submitted as an edit but got rejected and I don't yet have enough reputation to post a comment on his answer...

like image 24
Christoffer Årstrand Avatar answered Nov 05 '22 13:11

Christoffer Årstrand