- 12Increment Version and Build Numbers for iOS and Android apps using EAS1m 37s
Increment Version and Build Numbers for iOS and Android apps using EAS
Share this video with your friends
Set the build number to increment automatically and learn when to increment version numbers.
While you’re developing your app, when you submit an app with a specific version + version code to the App or Play Store, you cannot submit another app with the same values.
The best practice is to set the build number to increment automatically.
The version number can be incremented manually after each store release.
📖 Docs
This video's title is how to up the version and Build number but you are only covering the build number. Still very useful but you should rename the title or maybe I am going to be cheeky and suggest extending the video to cover the version too? :D
This video's title is how to up the version and Build number but you are only covering the build number. Still very useful but you should rename the title or maybe I am going to be cheeky and suggest extending the video to cover the version too? :D
Appreciate the feedback! I guess the idea of what I was trying to get across is that there are two values that uniquely identify your app, and while you can (and should) automatically version your builds, you can't (and shouldn't) use automatic versioning for the actual app version. It just doesn't work with how the native app store approvals are designed. Or at least I can't think of any automated way of doing it outside of a human knowing they've published a build and now it's time to increment to a new version.
Yeah makes sense. I have found ways to version it using packages in the past. Looking at the Expo docs it looks like you can do something like eas build:version:set In case you want to set the version. I have no used it yet though so I ll will let you know when I do. 🫡 Thank you very much for the content its great!