You have already setup your app on Bitrise, and now you are ready to start to deploy the app to your users or QA. There might be several versions going out and it might cause you some headache if you cannot identify these versions easily. Why have conflicting merges and misunderstandings and long conversations on who did or didn't fix what or when... You can easily refer to the exact build on Bitrise if you get an error report from a tester. Differentiate the versions to know who uses which and to make sure everybody uses the up-to-date app! Use (semi)automated version control on Bitrise too! 🤓
In software versioning a typical version identifier consists of 3 numbers, divided by full stops, e.g.: 3.4.2 (major.minor.build) Numbers are generally assigned in increasing order and correspond to new developments in the software.
Versions should be tracked in git repository. You can set version numbers in Info.plist, and you can update them manually there too. It is advised to do set the major and minor numbers by hand to be able to manage versions as you can decide which is a bigger or a smaller update. As for the build numbers, in a CI/CD environment it is useful to update the build while the build is happening.
On Bitrise there are steps to do just that: Set Xcode Project Build Number for iOS and Set Android Manifest Version Code and Name for Android. These steps insert the build number into the info.plist. If you did track versions otherwise earlier, you can offset these numbers to your existing numbering, so you don't have to start it all over again.
This is how it looks in reality for Android:
... and for iOS:
Happy version counting! 🔢