I uploaded a build using the Xcode beta, forgetting that you can't submit builds compiled with beta versions. So I updated to the release version of Xcode via the App Store.
With the Xcode beta, App Store Connect was accurately reflecting the build number (4.8.1). Now with the release version, Connect shows a build number of 5. I tried incrementing in Xcode to 4.8.2, and now Connect showed a build number of 6.
Has this happened to anyone else?
Are you confusing the "Version" number with the "Build" number?
• A Version number is typically something like 1.4.3
• A Build number is generally an integer, like 6
Build numbers must always increase... each App Store Connect upload must have a higher Build number.
Are you using any code to automatically increment your Build number?
Same here. I used the "Version" textfield like "1.5" and the "Build" textfield like "1.5.11". Worked fine for the last five years. In App Store and Testflight it always showed "1.5.11". Since two weeks (maybe XCode Update for iOS 15) it shows "(3)". Number depending on how often i build the app.
I experienced the same issue with XCode 13 GM and finally found the cause: during the process of uploading the archive, you are presented with a dialog that includes a "Manage Version and Build Number" checkbox. By default, it is ticked (i.e. checked). Untick this box to prevent the build number from being auto-managed by Apple. I'm not sure whether this is a new field or the default setting changed but XCode 13 GM is my first experience with this issue.
Now the question is how to get newly uploaded builds to be recognized by TestFlight, as my manually-managed build number is less than the last auto-managed number. This seems to prevent beta users from being notified of these newer builds even after I expired the earlier builds.
Thank you! This same thing happened to me and I have been incrementing the build by .1 for 2 years. Now with the new Xcode they change it. Whoa! I think that should be something that has more attention drawn to it.
With Xcode Cloud you can't currently uncheck "Manage Version and Build Number", I hope they will add this checkbox as well
NealK is damn right, just found out that if you don't uncheck the already checked option of Managing Version and Build Number and your archive's build number doesn't meet app store connect requirements then apple will change the version and build number automatically.