I have just updated to Xcode 13 Beta and I am about to upload my first build to App Store using this version of Xcode. This version of Xcode shows a new App Store Connect distribution option which I previously haven’t seen:
Manage Version and Build Number
This will change the version and build number of all content in your app to 1.2 (3).
I have already increased my version and build number from Xcode before archiving. What should we do here? If it is an automated way of build increment, what are the benefits of using it?
3
Answers
If you are sure that you have already updated your version/build number before archiving, then you can uncheck this and this will be ignored.
It provides you a chance to change
version
/build
just in case you forgot about it. There was no indication for this in previous Xcode versions.It allows you to change
version
/build
number before export/upload (after archiving), previously you had to create a new archive if you wanted to change theversion
/build
number.i ran into something unexpected with this – it also changes version numbers of frameworks embedded into the app.
https://developer.apple.com/forums/thread/690647
For folks using fastlane and struggling with Xcode changing build version.
New in Xcode 13:
When using fastlane for building and releasing apps, you can pass "manageAppVersionAndBuildNumber: false" parameter to export_options of build_app action to disable xcode version change.