Auto increment buildNumber(iOS) and versionCode(Android)
complete
Ishan
Currently, if we ever forget to increment the buildNumber or versionCode, the only point of time when we realize is when we are almost done uploading our APK or IPA file. That's when we are shown the error.
This wastes a lot of time. Requesting expo team to add an optional argument to expo build command which automatically increments the buildNumber and versionCode.
Or else, we should be shown a warning message when trying to build with same version code, and asked whether we want to continue or increment.
Thanks. Hope it is implemented soon.
Kim Brandwijk
complete
This feature is available on both platforms for EAS builds through the
autoIncrement
field in eas.json
. For more information on how to configure this, check out the documentation here.Kim Brandwijk
complete
This feature is available on both platforms for EAS builds through the
autoIncrement
field in eas.json
. For more information on how to configure this, check out the documentation here.Jesphin J
Can anyone have any solution for auto incrementing build number and version for react-native apps(ios and android)
Michael Wood
Jesphin J: Did you have a look at this? https://dev.to/bycedric/simplify-expo-releases-with-standard-version-2f4o
Jesphin J
Michael Wood: Yes, but I think the above is used for expo. I am using react-native init app
Michael Wood
Jesphin J: Ah, well I suspect something similar might work for you then, but this feature request list is specifically about Expo.
Jesphin J
Michael Wood: ok
Summer Syed
Jesphin J: Michael Wood Is it possible to use it with EAS?
A
ARTUR DE PAULA RIBEIRO
Jesphin J: In your CI tool do the auto increment during the pipeline. I use Bitbucket and put the pipeline execution number in versionCode (android) and buildNumber (ios). I use the "json" command line utility to make changes to the app.json file at pipeline time.
Pipeline code script example for bitbucket:
- npm install -g json
- json -I -f app.json -e "this.expo.ios.buildNumber='$BITBUCKET_BUILD_NUMBER'"
- json -I -f app.json -e "this.expo.android.versionCode=$BITBUCKET_BUILD_NUMBER"
- git pull
- git add app.json
- git commit -m "[skip ci] build updated to $BITBUCKET_BUILD_NUMBER"
- git push
Michael Wood
Adam Gerthel
Is there a reason why build number should ever be manually created? I mean, if the codebase has changed, then the version should've been updated. If the codebase hasn't changed, then a fresh build
should
be identical to the previous build - unless there was an issue during the creation of the build. Right? And if so - why not always generate a random ID for each build? I mean, a build ID should be unique for the build itself, not the code. Or am I missing something?A
Andrea Maschio
this would be so incredibly useful. If I count how many times this happened to me I think I could go in vacation with the time I would spare
Matt Goodwin
Yes, I echo the other users that the wasted time that occurs when this is forgotten is a constant source of headache.
A. Jonathan
Maybe not an auto increment but an extra step during the build, because maybe you could make a build incremented and after remember you forget something so the number would increment for no reason.
But yes it happens often that I forget to change the versionCode on Android and I have to rebuild again
+ the problem is that you are only informed after to upload on the Play store, so you loose that time as well
Jay Jackson
This is a must have feature for my team. Wrapping something like semantic would be a great first step.
Raphael Rouvinov-Kats
Having a warning message when building with a previously-used version code would be very nice. I've made this mistake many times
Philihp Busby
Would love to see this happen. When I used Appcenter to manage my builds, it injected this number before every build.
Load More
→