Increment the build number of your project
|Supported platforms||ios, mac|
|Returns||The new build number|
increment_build_number # automatically increment by one
increment_build_number( build_number: "75" # set a specific number )
increment_build_number( build_number: 75, # specify specific build number (optional, omitting it increments by one) xcodeproj: "./path/to/MyApp.xcodeproj" # (optional, you must specify the path to your main Xcode project if it is not in the project root directory) )
build_number = increment_build_number
||Change to a specific version. When you provide this parameter, Apple Generic Versioning does not have to be enabled|
||Don't update Info.plist files when updating the build version||
||optional, you must specify the path to your main Xcode project if it is not in the project root directory|
* = default value is dependent on the user's system
Actions can communicate with each other using a shared hash
lane_context, that can be accessed in other actions, plugins or your lanes:
increment_build_number action generates the following Lane Variables:
||The new build number|
To get more information check the Lanes documentation.
To show the documentation in your terminal, run
fastlane action increment_build_number
It is recommended to add the above action into your
Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal
fastlane run increment_build_number
To pass parameters, make use of the
: symbol, for example
fastlane run increment_build_number parameter1:"value1" parameter2:"value2"
It's important to note that the CLI supports primitive types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g.
param:"1,2,3"). Hashes are not currently supported.
It is recommended to add all fastlane actions you use to your
This action, just like the rest of fastlane, is fully open source, view the source code on GitHub