Version code 1 has already been used. Try another version code

Question

I am uploading new app bundle to play console and it is saying after uploading Version code 1 has already been used. Try another version code.

I have changed version number in pubspec.yaml from version number: 1.0.0+1 to 2.0.0+1 even though it is saying the same error

In my case, I have an updated version but the upload wasn't successful, So the version was uploaded but not added to the release. when I tried to re-upload it, I got that error. the solution in that case is selecting it from the library (no need to generate a new version)! — Shady Mohamed Sherif, Mar 28 '22 at 19:04

score 49 · Answer 1 · edited May 13 '22 at 10:35

49

You have two ways to solve this, if you released your bundle already, then you have to update your version code like in Len_X's answer,

If you're still developing and pushed app bundle for say, testing, and then you delete it, this bundle is saved as a draft with that version code. Therefore, it says that you can't use the same version because it already sees another one with the same version name.

Here's how you fix it:

Go to the release section
go to app bundle explorer, in the top right you should see a dropdown button for you app version, click on it.
A bottomsheet will show containing all the previous app bundles you uploaded it. Delete the one with clashing bundle version and you're good to go.

Hope that solves your problem.

edited May 13 '22 at 10:35

Itai Dagan

287
2
11

answered Jun 20 '21 at 17:39

Michael Soliman

1,190
1
5
18

This is not a maintainable solution. – Len_X Jun 21 '21 at 09:08
4

@Len_X this solution is only for pre-releasing, if you release your app, then your solution is the right way – Michael Soliman Jun 22 '21 at 11:11
2

Thanks for the 2nd option (app bundle explorer). I had created a release and it was denying my upload. Didn't want to increment +1 to keep iOS version paired. – ce-loco Jul 07 '21 at 17:23
3

I can't see the "delete" option when I click on the dropdown, next to app version. Does it still work? – Jay N Nov 07 '21 at 20:14
This is what I was looking for as I had to update the bundle before publishing it. – gildniy Dec 20 '21 at 07:22
Even when you pre-release, you can increment the version code number! It's not the same as the version name, after all. I just published my blackbox version 1.0.0 with the version code 18. The user sees only "1.0.0". The "18" is only for Play Store. – Karolina Hagegård May 13 '22 at 07:40
@MichaelSoliman how to delete the app bundle in the bottomsheet? (step 3) , I can't find delete button/icon on the bottom sheet like this: https://i.stack.imgur.com/oFK0L.png – Alexa289 May 31 '22 at 09:55

score 47 · Answer 2 · answered Jul 13 '21 at 14:19

You can do it manually by going to "app_name/android/app/build.gradle" file. In defaultConfig section change version code to a higher number

  defaultConfig {
        applicationId "com.my.app"
        minSdkVersion 23
        targetSdkVersion 30
        versionCode 1 // Change to a higher number
        versionName "1.0.1" // Change to a higher number
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
        javaCompileOptions {
            annotationProcessorOptions {
                arguments = ["room.schemaLocation": "$projectDir/schemas".toString()]
            }
        }
    }

score 22 · Answer 3 · answered Sep 22 '21 at 15:45

22

First go to the app/build.gradle

change versionCode and versionName like this (+1)

I think this will be helpful for someone ✌

answered Sep 22 '21 at 15:45

hexhad

851
10
12

3

Super confusing to keep track of. – serraosays Sep 30 '21 at 15:23
However, this is just "default configurations"... Doesn't all the other code in the `android/app/build.gradle` file sometimes over-write the default values? Or this over-writes the other code?... In any case, feels like there is some proper way to do it, that we haven't yet figured out. – Karolina Hagegård May 13 '22 at 07:36

balu k · Answer 4 · 2022-05-05T10:07:17.117

14

For Flutter only: Goto Pubspec.yaml file and find version key and Change the value after the + sign.

For Example: In your pubspec.yaml file, if your version is like this version: 1.0.0+1 then change it to version: 1.0.0+2

edited May 05 '22 at 10:07

answered Nov 03 '21 at 09:57

balu k

1,869
1
8
25

The number after the "+" sign is version code – balu k May 14 '22 at 12:34
No, it isn't!... You don't even have to put a number after the plus sign of you don't want to! You can just put "1.0.1" for example. – Karolina Hagegård May 17 '22 at 22:46

score 12 · Answer 5 · answered Jun 20 '21 at 16:42

12

You have to increment the +1, it should be +2 to indicate build number

answered Jun 20 '21 at 16:42

Len_X

727
10
27

3

Shouldn't the build number be "scoped" from within the version number? `1.0.0+1` and `2.0.0+1` are obviously not the same version... – mgalgs Aug 13 '21 at 23:13
@OshMansor, by OP do you mean Len_X or balu k? Changing the version from `1.0.0+1` to `1.0.0+2` _or_ `2.0.0+1` should avoid the issue. Or are we saying that's not the case? If you increment the major version number, do you also need to increment the revision number? That is, `1.0.0+1` to `2.0.0+1` won't solve this issue, but `1.0.0+1` to `2.0.0+2` will? – Brandon Essler Oct 10 '21 at 16:01
1

@BrandonEssler OP=Len_X. And yes only your latter case would work i.e. `1.0.0+1` to `2.0.0+2`. I tried the former and it still would not let me pass the submission. – Osh Mansor Oct 12 '21 at 06:31
It's so confusing to delete the existing aab, I just couldn't and now the worst has happened, my apple version is 1.0.1 whereas my android is on 3.0.0(3).... – Aditya Peshave Dec 25 '21 at 01:18

score 5 · Answer 6 · answered Dec 07 '21 at 10:50

5

if you remove apk then upload same version apk so you get Error Version code 1 has already been used. Try another version code in this situation you should remove version from App bundle explorer then upload same version apk.

answered Dec 07 '21 at 10:50

adarsh

124
1
5

This is the simplest way if you are not ready to increment the version number in your bundle. It worked for me! – charles young Feb 18 '22 at 22:27
However, there is a point with version code numbers! If you do it this way, you're missing that point. – Karolina Hagegård May 13 '22 at 07:32

score 3 · Answer 7 · answered Sep 30 '21 at 16:01

If you're running into app bundle approval issues inside of the Google Play store with an Expo/React Native project, here are some tips:

Google Play versioning is actually checking your AndroidManifest.xml file for versioning (/android/app/src/). This should get updated from Expo's app.json file (/app.json) during build, per their instructions.

app.json example section, where I've bumped my app up to a v2.0 - note the versionCode inside of the Android settings object AND the version at the settings object root both need to be adjusted:

{
  "name": "app-name",
  "displayName": "App Name",
  "expo": {
    "android": {
      "package": "app.here",
      "permissions": [],
      "versionCode": 2
    }
  },
  "version": "2.0.0"
}

If your Android version isn't updating (possibly if you have a detached Expo app), you have to go directly into the AndroidManifest.xml file and make the modification there (/android/app/src/):

Example of AndroidManifest.xml (note your modifications happen on the <manifest> tag, using the android:versionCode and android:versionName:

<manifest 
  xmlns:android="http://schemas.android.com/apk/res/android" 
  package="com.aganashapp"
  android:versionCode="2"
  android:versionName="2.0"
>
  <uses-permission android:name="android.permission.INTERNET"/>
  <application
    android:name=".MainApplication"
    android:label="@string/app_name"
      android:icon="@mipmap/ic_launcher"
    android:allowBackup="false"
    android:theme="@style/AppTheme"
  >
    <meta-data android:name="expo.modules.updates.EXPO_UPDATE_URL" android:value="https://exp.host/@username/app-name" />
    <meta-data android:name="expo.modules.updates.EXPO_SDK_VERSION" android:value="42.0.0" />
    <meta-data android:name="expo.modules.updates.EXPO_RELEASE_CHANNEL" android:value="default" />

  <activity
    android:name=".MainActivity"
      android:label="@string/app_name"
      android:configChanges="keyboard|keyboardHidden|orientation|screenSize|uiMode"
      android:launchMode="singleTask"
      android:windowSoftInputMode="adjustResize"
      android:theme="@style/Theme.App.SplashScreen"
    >
      <intent-filter>
        <action android:name="android.intent.action.MAIN"/>
        <category android:name="android.intent.category.LAUNCHER"/>
      </intent-filter>
    </activity>
    <activity android:name="com.facebook.react.devsupport.DevSettingsActivity"/>
  </application>
</manifest>

If you're still having issues, remember that Android versionCode and versionName are two different things. Android does not seem to recognize semver standards. versionCode increments as whole numbers (ie, if you went from semver v1.0.0 to v1.1.0 that is versionCode 1 to 2.

score 0 · Answer 8 · answered Aug 30 '21 at 09:08

0

If you get the above error in the google play console, please change the version: in pubspec.yaml.

Reference. How to set build and version number of Flutter app

and me works

answered Aug 30 '21 at 09:08

Ryosuke Hujisawa

2,322
1
12
15

and you need `% flutter build appbundle --release` again – Ryosuke Hujisawa Aug 30 '21 at 09:12
Weird that this works for you!... This has never worked for me. Also "version" and "version code" are not the same thing so... your SDK automatically increments your version code when you change your version name? – Karolina Hagegård May 13 '22 at 06:58

score 0 · Answer 9 · answered Mar 27 '22 at 11:11

with my flutter project building a release for android i faced the same issue. all was doing is change version code in Pubspec.yaml but did not seem to change my android version... so i went to Android folder and added version code manually in local.properties file : /project/android/local.properties

flutter.versionName=1.1.0

flutter.versionCode= from 1 to 4

score 0 · Answer 10 · edited Apr 02 '22 at 16:33

0

The first step change the version code
The second step go to the other settings and change the bundle version code as well

edited Apr 02 '22 at 16:33

Martin Braun

8,191
8
54
91

answered Apr 01 '22 at 08:27

Look Dev

9
1

If the person who asked knew how to change the "version code" they probably wouldn't have the error to begin with, though. Try and include some steps in your answer, so that people can actually follow them! – Karolina Hagegård May 12 '22 at 18:20

Karolina Hagegård · Answer 11 · 2022-05-13T07:56:20.663

I always used to increment version code in my android/app/build.gradle file, and it always used to work. Then, after a recent update in Android Studio, it suddenly didn't anymore, and I got this error!

I never cared to dig into the build.gradle code, but now, I did. Here, at the "TODO", is where I used to change the version code number:

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new FileNotFoundException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '19' // TODO: ---Count up with each release
}

But that only works if the version code from the local.properties file comes back as "null"!... I just realized. So probably, all this time, my compiler never managed to get values from local properties, but now all of a sudden, it does!

So I found the android/local.properties file and tried changing the version code there:

sdk.dir=C:\\Users\\karol\\AppData\\Local\\Android\\sdk
flutter.sdk=C:\\src\\flutter
flutter.buildMode=release
flutter.versionName=1.0.0
flutter.versionCode=1   //Change this to 19 (my current version code number)

But that didn't work, because the moment I ran flutter build appbundle, this file changed itself back to the original values...

I then tried adding version code values to my AndroidManifest.xml file, according to serraosays' answer, but that didn't help me either.

Functioning work-around

In the end, I did this in the android/app/build.gradle file:

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
//if (flutterVersionCode == null) {
    flutterVersionCode = '19' // TODO: ---Count up with each release
//}

That is, I commented out the condition. Now, my setting would over-write any value retrieved from the local.properties file.

If anyone can tell me the proper way to increment the version code number, I'm all ears! But in the meantime, this worked for me, and hopefully for someone else as well.

score 0 · Answer 12 · answered May 18 '22 at 11:15

There are two reasons for this error:

First, is common given in other answers: you must increase the version number to send an update to Play Console. Eg. previous app version: 1.0.5+5 and next update must contain 1.1.2+6. The +6 must be next to the previous update present on your play console.
Second reason for this error is you have skipped some numbers in between. Eg. Previous released version: 1.0.5+5 but the new version you are trying to release is 1.0.6+8. The +8 is not allowed directly, you must put +6 then +7 and then next numbers.

Version code 1 has already been used. Try another version code

12 Answers12

Functioning work-around

Linked