There is a way to auto increment buildNumber/versionCode?

[gabsdotco]

Hello! I'm building a expo app using expo-dev-client and I need to publish the app to the store. The problem is, everytime I make a publish to the store an error occurs saying that I need to increment the versionCode/buildNumber because a binary already have that code published on the store and I understand that, but there is a way to auto increment that?

Like, I want to create a publish action on github and always having to increment manually is not cool.

[b0iq]

@kbrandwijk says:

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.

[gabsdotco]

Thank you so much for this!

[calderwoodra]

Seems like this doesn't cover expo.version from what I can tell, which the apple app store will block if a duplicate is uploaded.

yarn run v1.22.19
$ eas build -p ios --profile production --auto-submit --no-wait
    InvalidEasJsonError: eas.json is not valid.
    - "build.production.autoIncrement" must be a boolean
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[brentvatne]

@calderwoodra - that is correct. we expect that users typically want to bump the version on their own since that is visible to users and is often used to communicate some meaning. we may add support for auto incrementing that in the future though! for now we just handle buildNumber and versionCode

[konjoinfinity]

It’s not obvious in the docs, it must be under the build section in eas.json:

"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"channel": "development",
"autoIncrement": true
},

[jagdish1o1]

Dropping this link for more details.

App version management with Expo CLI

https://docs.expo.dev/build-reference/app-versions/

[boblitex]

is there a way to achieve this even while having a dynamic config (app.config.js)

[brentvatne]

yup, use the remote version source: https://docs.expo.dev/build-reference/app-versions/#remote-version-source

it's recommended in most cases anyhow