problems with Google Play Developer Console - uploading APK

Other
#1

Hi,

I am having a random problem when uploading new versions to google play store via the developer console.

Sometimes, but not all the time. I get the following message:

"Upload failed

You need to use a different version code for your APK because you already have one with version code 3."

Using this example, I have built the new version in Corona for android with version = 4 and version name = 1.4. this builds correctly but I get the above message.

Is this an issue with Google or Corona.

I can see elsewhere that you can put the version number in the build settings (or config, cant remember which) but I assumed this has been overtaken by the versions in the build dialog.

thanks

Martin

#2

Are you sure you are uploading the right APK?  The issue is over the Version Code value.  That is the identifier that Android uses to determine version.  So if during the build process you are specifying 4 for the Version Code, but when you upload it to Google Play it lists as a Version Code of 3, that is odd.

Years ago, you could put Version Code and Version Name in the build.settings file, but you shouldn’t do that anymore.  You should just specify it in the Build dialog when you do the build.  (At least, I cannot think of any reason why you would keep it in the build.settings file.)  If you do have it in there, remove it and be sure to just specify it in the Build dialog.

#3

Hi thegdog,

that’s what I thought at first. I went into a frenzy checking it wasn’t finding an old apk somewhere. Upshot was that I solved the problem empirically by jumping a version code, ie it was 3 and should have accepted 4, but it did accept 5!!!

I didn’t try the embedding in buildsettings as I guessed this might break the build process putting its version in.

I now know how to get it to work (I think!) but it is very inelegant jumping a number because of a bug somewhere. Ive asked google too.

thanks for trying.

Martin

#4

Do you have a version code in your build.settings?

Rob

#5

No, I only use the version code and version name in the build dialog.

Martin

#6

That is strange.  Never had that happen myself.

#7

I don’t recommend putting them in build.settings because it’s easy to forget its there and it can burn you.

As for why you’re getting that error I would only guess to make sure you check the timestamp on the file and make sure you’re grabbing the right file.  Maybe you’re picking the build up from a different folder than Corona is outputting to.  Also make sure you don’t output your build to your project folder.

Rob

#8

Are you sure you are uploading the right APK?  The issue is over the Version Code value.  That is the identifier that Android uses to determine version.  So if during the build process you are specifying 4 for the Version Code, but when you upload it to Google Play it lists as a Version Code of 3, that is odd.

Years ago, you could put Version Code and Version Name in the build.settings file, but you shouldn’t do that anymore.  You should just specify it in the Build dialog when you do the build.  (At least, I cannot think of any reason why you would keep it in the build.settings file.)  If you do have it in there, remove it and be sure to just specify it in the Build dialog.

#9

Hi thegdog,

that’s what I thought at first. I went into a frenzy checking it wasn’t finding an old apk somewhere. Upshot was that I solved the problem empirically by jumping a version code, ie it was 3 and should have accepted 4, but it did accept 5!!!

I didn’t try the embedding in buildsettings as I guessed this might break the build process putting its version in.

I now know how to get it to work (I think!) but it is very inelegant jumping a number because of a bug somewhere. Ive asked google too.

thanks for trying.

Martin

#10

Do you have a version code in your build.settings?

Rob

#11

No, I only use the version code and version name in the build dialog.

Martin

#12

That is strange.  Never had that happen myself.

#13

I don’t recommend putting them in build.settings because it’s easy to forget its there and it can burn you.

As for why you’re getting that error I would only guess to make sure you check the timestamp on the file and make sure you’re grabbing the right file.  Maybe you’re picking the build up from a different folder than Corona is outputting to.  Also make sure you don’t output your build to your project folder.

Rob

#14

thanks Rob, :slight_smile:

i had the same issue and resolve it by removing the version # from the build file.

Regards

Abdul

#15

thanks Rob, :slight_smile:

i had the same issue and resolve it by removing the version # from the build file.

Regards

Abdul