autoIncrement option is not supported when using app.config.js

[cchbr]

Build/Submit details page URL

No response

Summary

The following error is received when trying to eas build with autoIncrement set to true in eas.json.

autoIncrement option is not supported when using app.config.js

Shouldn't this be supported? It is a new project with all the latest versions.

Managed or bare?

Managed

Environment

  expo-env-info 1.2.0 environment info:
    System:
      OS: Windows 10 10.0.19045
    Binaries:
      Node: 18.0.0 - C:\Program Files\nodejs\node.EXE
      npm: 7.20.4 - C:\Program Files\nodejs\npm.CMD
    npmPackages:
      expo: ~50.0.7 => 50.0.7
      react: 18.2.0 => 18.2.0
      react-native: 0.73.4 => 0.73.4
    Expo Workflow: managed

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check for issues with metro config
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK

Didn't find any issues with the project!

Error output

No response

Reproducible demo or steps to reproduce from a blank project

{
  "cli": {
    "version": ">= 7.2.0",
    "promptToConfigurePushNotifications": false
  },
  "build": {
    "development": {
      "env": {
        "API_URL": "http://192.168.0.108:8080/rest/"
      },
      "developmentClient": true,
      "distribution": "internal"
    },
    "preview": {
      "distribution": "internal",
      "env": {
        "API_URL": "http://test.api.com/rest/"
      }
    },
    "production": {
      "env": {
        "API_URL": "http://api.com/rest/"
      },
      "autoIncrement": true
    }
  },
  "submit": {
    "production": {}
  }
}

[szdziedzic]

Hi, I think this is a good use case for https://docs.expo.dev/build-reference/app-versions/#remote-version-source

If you set { "cli": { "appVersionSource": "remote" } } in your eas.json the version code is managed and incremented server side.

[szdziedzic]

Forgot to mention but you can also do https://docs.expo.dev/workflow/configuration/#dynamic-configuration