Trying to publish to GooglePlay appStore gives error 403

Question

Trying to upload the version 39 of the app, the error message I get is:

Error uploading 'foo.bar.baz'

Version 38 of this app cannot be downloaded by any devices as they will all receive APKs with higher version codes. [403]

Screenshot:

What does this exactly mean? I'm trying to publish as "Alpha" from VisualStudio for Mac (the current version 38 of the alpha channel was uploaded manually.)

yes I did, it's 36 while the latest in the GooglePlay console is 35 — knocte, Jul 20 '18 at 09:24
I suspect you still have APK version code 1 as a "retained APK" in your release. Can you show a screenshot of your "manage releases" page. I suspect you still have an on version code 1 around. — Nick Fortescue, Jul 23 '18 at 07:31
now everything on the Alpha lane, still similar error message (see edits and screenshot) — knocte, Jul 31 '18 at 09:20
Can you check this https://stackoverflow.com/questions/16060655/what-does-this-google-play-apk-publish-error-message-mean — FreakyAli, Aug 02 '18 at 07:53
From the screenshot it appears you're trying to publish apk with version 39 and error is for apk with version 38. Please see that you have deactivated apk with version 38 like others have mentioned. — random, Aug 03 '18 at 05:00

score 0 · Answer 1 · answered Jul 20 '18 at 09:12

0

The Version number (integer-based) is set via the versionCode in the manifest must be increased each time you submit to the Play Store no matter if it is submitted as an Alpha, Beta, or Release APK.

Either via the Project Options / Build / Android Application :

Or via manually editing the AndroidManifest.xml:

android:versionCode="18"

answered Jul 20 '18 at 09:12

SushiHangover

73,120
10
106
165

yeah I already increased that, it's bigger than the latest release – knocte Jul 20 '18 at 09:23
@knocte ? The error says `Version 1` . Version Number and Name are different, Name is just that a name, it can be anything and is what is shown to the user, the Number (`versionCode`) has to be incremented upon every submission, wether or not that apk is ever released – SushiHangover Jul 20 '18 at 09:28
it's weird, I don't know where does that number `1` come from then – knocte Jul 20 '18 at 10:13
@knocte That number comes from `versionCode` in the manifest and thus `Version name` in the project options. – SushiHangover Jul 23 '18 at 15:18
nope, in Version number I have the value `36` and in Version name I have the value `0.4.0.36` – knocte Jul 24 '18 at 03:11
@knocte Try double checking the final manifest in the apk just to sure. – SushiHangover Jul 24 '18 at 03:12
it's correct, I double checked, because uploading the APK manually works – knocte Jul 24 '18 at 06:19
I updated the answer to now not involve the InternalTest lane at all, just the alpha, see screenshot. – knocte Jul 31 '18 at 09:20

score 0 · Accepted Answer · answered Aug 07 '18 at 08:12

0

Seems to be a bug in Visual Studio for Mac, so I reported it here. Hopefully they fix it soon.

answered Aug 07 '18 at 08:12

knocte

16,941
11
79
125

score -1 · Answer 3 · answered Aug 03 '18 at 17:11

-1

If I remember correctly I've had a similar issue when I was trying to update an apk with higher version code to beta, when there was still apk with lower version code in alpha.

Since you are trying to upgrade on alpha, maybe you have an apk on internal test track with version code 38? If that is the case, I would deactivate version uploaded to internal test tract (or update it to version code 39) and then update version on alpha

answered Aug 03 '18 at 17:11

Krzysztof Wrona

311
5
12

how to deactivate it? I don't find the option to do it – knocte Aug 06 '18 at 03:41
there's no UI in the GooglePlay Console website to deactivate releases, only way to do it now seems to be when rolling out a new release manually – knocte Aug 06 '18 at 08:59

Trying to publish to GooglePlay appStore gives error 403

3 Answers3