Ctrl+Z Therapy
CasesQuick answersGuides10-minute checklistHow we testCartoonSend it in

Google Play rejects your new build? The versionCode must be new (Expo autoIncrement)

Ship ItChecked against the official source

Source checked 8 Nov 2026 · Published 9 Nov 2026 · Last reviewed 9 Nov 2026 · By Ctrl+Z Therapy (how we test)

The short answer

Android's versioning docs: you can't upload an APK to the Play Store with a versionCode you have already used for a previous version. The versionCode is a number for the store, separate from the versionName people see. With Expo, it's android.versionCode in your app config, and Expo can increment it for you.

What to do

  1. In eas.json, set cli.appVersionSource to remote, so Expo servers manage android.versionCode and ios.buildNumber.
  2. Set autoIncrement to true on your production build profile.
  3. Create a new production build: the versionCode and buildNumber are incremented automatically.

Good to know

  • The remote version starts from the value in your local project.

Source

Checked on 8 Nov 2026. Prices, limits and settings change, so check the source before you rely on them.

Related