Created
July 24, 2012 20:44
-
-
Save sekati/3172554 to your computer and use it in GitHub Desktop.
Xcode Auto-increment Build & Version Numbers
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # xcode-build-bump.sh | |
| # @desc Auto-increment the build number every time the project is run. | |
| # @usage | |
| # 1. Select: your Target in Xcode | |
| # 2. Select: Build Phases Tab | |
| # 3. Select: Add Build Phase -> Add Run Script | |
| # 4. Paste code below in to new "Run Script" section | |
| # 5. Drag the "Run Script" below "Link Binaries With Libraries" | |
| # 6. Insure that your starting build number is set to a whole integer and not a float (e.g. 1, not 1.0) | |
| buildNumber=$(/usr/libexec/PlistBuddy -c "Print CFBundleVersion" "${PROJECT_DIR}/${INFOPLIST_FILE}") | |
| buildNumber=$(($buildNumber + 1)) | |
| /usr/libexec/PlistBuddy -c "Set :CFBundleVersion $buildNumber" "${PROJECT_DIR}/${INFOPLIST_FILE}" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # xcode-version-bump.sh | |
| # @desc Auto-increment the version number (only) when a project is archived for export. | |
| # @usage | |
| # 1. Select: your Target in Xcode | |
| # 2. Select: Build Phases Tab | |
| # 3. Select: Add Build Phase -> Add Run Script | |
| # 4. Paste code below in to new "Run Script" section | |
| # 5. Check the checkbox "Run script only when installing" | |
| # 6. Drag the "Run Script" below "Link Binaries With Libraries" | |
| # 7. Insure your starting version number is in SemVer format (e.g. 1.0.0) | |
| # This splits a two-decimal version string, such as "0.45.123", allowing us to increment the third position. | |
| VERSIONNUM=$(/usr/libexec/PlistBuddy -c "Print CFBundleShortVersionString" "${PROJECT_DIR}/${INFOPLIST_FILE}") | |
| NEWSUBVERSION=`echo $VERSIONNUM | awk -F "." '{print $3}'` | |
| NEWSUBVERSION=$(($NEWSUBVERSION + 1)) | |
| NEWVERSIONSTRING=`echo $VERSIONNUM | awk -F "." '{print $1 "." $2 ".'$NEWSUBVERSION'" }'` | |
| /usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString $NEWVERSIONSTRING" "${PROJECT_DIR}/${INFOPLIST_FILE}" |
If you want to keep $(MARKETING_VERSION)
in Info.plist for CFBundleShortVersionString but
want to increase version after successful archive or build
then use following script
following script will increase like 1.0 to 2.0
but of-course that logic can be modified using above explained gist etc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From Xcode 13, a new project will not generate an info.plist. Instead this is embedded in the project.
If you want a project to generate an Info.plist, set
Generate Info.plist filetonoand then open the Info tab and add a option (e.g.App Transport Security Settings). Xcode will then generate the Info.plist file and add all the values as well as update the build settings.