Almost every Android developer hits this error on their second upload to Google Play Console. You drop a freshly built .aab into App bundles on Step 1 — Create release, and Play Console rejects it immediately in red text:
Version code <X> has already been used. Try another version code.
(If you deploy via Fastlane, GitHub Actions, or the Google Play Developer API, the same rejection comes back as APK specifies a version code that has already been used.)
Two Play Console rules catch first-time publishers by surprise here:
versionCodeis notversionName. Changing the user-visible version string from1.0.0to1.0.1does nothing on its own. Play Console identifies builds strictly by their positive integerversionCode(1,2,3…).- Every uploaded
.aabburns itsversionCodepermanently. The moment an App Bundle finishes uploading into Play Console, that integer is reserved forever for your app—even if you clicked Discard draft release and never rolled it out, or only uploaded it to Internal testing.
Before you touch your build config and recompile, check whether your code actually changed—the right fix depends on which case applies.
1Didn't change your code? Use "Add from library" instead of re-uploading
You do not need a new versionCode (or a new build) if:
- You already tested a build on Internal testing and want to roll out that exact same
.aabto Closed testing or Production. - You uploaded an
.aabearlier, clicked Discard draft release (or closed the tab), and want to recreate the release with the same bundle.
Dragging the local .aab file into the upload box a second time fails because Play Console already has that artifact stored in your bundle library. Instead of re-uploading:
- Open your target track—for example, Test and release > Testing > Closed testing—and click Create new release.
- Inside the App bundles box, click Add from library (right next to Upload).
- Select the already-uploaded bundle (
versionCode <X>) from the list and add it to the release. - Fill in Release notes, click Next to Preview and confirm, and roll out.
2Changed your code? Increment versionCode in your framework
Whenever you fix a bug, change AndroidManifest.xml, update SDKs, or rebuild a new .aab, you must increase the integer versionCode by at least +1 before building.
Android Studio / Gradle
Open app/build.gradle.kts (or app/build.gradle) and increment versionCode inside defaultConfig:
android {
defaultConfig {
applicationId = "com.yourbrand.app"
minSdk = 24
targetSdk = 35
versionCode = 2 // Must increase by +1 (or more) on every new upload
versionName = "1.0.1" // Shown to users; Play Console ignores this for uniqueness
}
}
(In Groovy app/build.gradle, omit =: use versionCode 2 and versionName "1.0.1".)
Flutter
In pubspec.yaml, Flutter splits version at the + sign—versionName goes before +, and Android's integer versionCode goes after +:
# pubspec.yaml
version: 1.0.1+2
Run flutter build appbundle --release to build the new bundle, or override both values directly in CI without editing pubspec.yaml:
flutter build appbundle --release --build-name=1.0.1 --build-number=2
If Play Console still complains about versionCode 1, open android/app/build.gradle(.kts) and check that versionCode still reads flutter.versionCode rather than a hardcoded integer.
Expo / React Native
If you build with EAS Build, let EAS manage and increment versionCode remotely so you never forget to bump it by hand—set "appVersionSource": "remote" and "autoIncrement": true in eas.json:
{
"cli": {
"appVersionSource": "remote"
},
"build": {
"production": {
"autoIncrement": true
}
}
}
If you keep versions in source control instead, increment expo.android.versionCode in app.json before running your build:
{
"expo": {
"version": "1.0.1",
"android": {
"versionCode": 2
}
}
}
(For bare React Native projects without Expo, update versionCode in android/app/build.gradle just like Android Studio.)
Unity
Open Edit > Project Settings > Player, switch to the Android tab, and expand Other Settings. Under Identification, Version (1.0.1) maps to versionName, while Bundle Version Code (2) maps to Android's integer versionCode. Increase Bundle Version Code by +1 and rebuild with Build App Bundle (Google Play) enabled.
3Forgot which versionCode you're on? Check Latest releases and bundles
After a couple of discarded drafts or CI builds, guessing whether your next integer should be 3 or 6 gets annoying fast.
In Play Console's left menu, open Test and release > Latest releases and bundles (and switch to App bundle explorer to see the full upload history). Every .aab ever uploaded to your app is listed there—including builds on Internal testing, paused tracks, and discarded drafts that never went live. Check the highest Version code at the top of the table and set your next build to at least highest + 1. Skipping numbers (for instance, jumping from 4 straight to 10) is completely valid as long as each new release uses a larger integer than the active one.
4Related error: "doesn't allow any existing users to upgrade"
Sometimes your versionCode passes Create release, only for Step 2 — Preview and confirm to block the rollout with a version-shadowing error:
You can't rollout this release because it doesn't allow any existing users to upgrade to the newly added app bundles.
Play Console throws this when no user on the track's current release can upgrade to the bundle in your draft:
- You picked an older bundle via Add from library: The track's active release is already on
versionCode 5, and you selectedversionCode 3or4. Google Play never downgrades existing installs on a track. - You clicked Next without adding a newer bundle: You started Create new release and moved to Preview and confirm with nothing new under App bundles.
- You narrowed device compatibility: Your new bundle has a higher
versionCode, but raisedminSdkVersion, dropped a required ABI (arm64-v8a), or added a strict<uses-feature>tag that excludes all previously supported devices.
To fix it, check the active versionCode shown under Previous release on that track, add an .aab with a strictly higher versionCode covering your target devices, and remove any lower-version bundle sitting in the same draft.
Why shipping multiple versionCodes helps pass your 14-day closed test
Running into another check on Preview and confirm—such as 16 KB memory page sizes, AD_ID permission mismatches, or yellow R8 and debug-symbol warnings? See the full Google Play Console AAB Upload Errors: Causes and Fixes guide.
Once your closed test begins on a personal developer account, bumping versionCode is more than a build formality. Leaving versionCode 1 untouched for 14 days makes it hard to prove real iteration when you apply for access to production; shipping 3 or more genuine updates (versionCode 2, 3, 4…) based on tester feedback builds a visible release history on your closed testing track and gives you concrete changes to cite in the questionnaire—one of the best safeguards against getting rejected with "More testing required".
Shipping updates only counts if testers actually keep your app installed and open those new builds. On BetaLobby (free, no paid plans), you can team up with 15 other developers in Team mode using one shared Google Group, with screenshot-free install checks and daily check-in tracking across all 14 days so every update you push gets opened on real phones.