Build number vs version number on iOS (CFBundleVersion)

An Apple app carries two numbers in its Info.plist. The version, CFBundleShortVersionString, is the user-visible release number, three period-separated integers such as 2.4.0. The build number, CFBundleVersion, identifies one iteration of the bundle: one to three period-separated integers such as 57. Xcode shows them as Version and Build; Expo calls the build number ios.buildNumber.

App Store Connect uses both. Apple says the bundle ID and version associate an upload with the app and its version record, and the build string identifies the build uniquely throughout the system. So an upload that repeats a build number Apple already has is refused, while one version can have many builds: 2.4.0 build 57, build 58 and so on, until one of them ships. Beta App Review works per version too: one build of each version in review at a time.

Android has the same pair: versionName for people and versionCode for the store.

In VibeView. Set "autoIncrement": true on the production profile and every production build gets the next number from a counter VibeView keeps per app and platform, passed to your build as VIBEVIEW_BUILD_NUMBER. For iOS and tvOS, with an App Store Connect key stored, the first number starts above the highest build App Store Connect already has (it checks the 200 most recent uploads). The Submit dialog’s Ready to send list checks the build number is newer than the latest TestFlight build, and Builds → Stores → your app → Edit → Build number raises the counter. See Automatic build numbers.