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.)
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"
Seems to be a bug in Visual Studio for Mac, so I reported it here. Hopefully they fix it soon.
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
Related
Months ago I uploaded an alpha app that I created using Expo on React Native. I build the app with the version 1.0.0 in app.json. The people involved with the project tested it, I improved it with some other things and we concluded it's ready to go to production.
The thing is Google Play Console returns error when I try to upload it. According to the message (number 2 in the below print), it says (in Portuguese) "You already have an APK or Android App Bunble with version 1 code. Use another code". What does that mean?
Basically, I uploaded it, improved it and now, want to upload it again with the new things.
I tried to upload it in alpha again, beta, build the app again with version 1.1.0 in app.json but, same error message. Has this version 1 code nothing to do with the version in app.json?
In the below print, we can see the main panel, where there is just one release, which is the alpha one. Any help would be great. Thanks for now.
------------------ EDIT -----------------------
According to an answer, I thought it would be good to put the print of app.json. I hid some private fields. As you can see, the version is 1.0.0, but I tried building a 1.1.0 and 2.0.0 version app. None of them solved the problem.
seems like your new app has a versionCode that conflicts with the existing app.
go to YOUR_APP/android/app/build.gradle and search for versionCode. increase the number by 1, recompile your .aab or .apk and upload again.
UPDATED
versionCode is missing. Can you add it like this?
“android”: {
“versionCode”: 2,
...
}
Our App Kidstriangle User installation from google play store works fine on Android 4,5,6 but we always get 504 error when install on Any Android 7
1. Already tried clear cache, clear data, login/out from store.
Any idea why this is specific to Android 7 only.
We are using google-play-service GCM:7.0.0 (used for notification) to get maximum comparability is that can be one of the reason?
1. Using latest Android studio and Graddle with targetSDK 25 and compiled with 25.0.3, minSDK 16
The Problem is if you are using android 2.2.2
1. release apk are aleardy algned avoid aligning them again
2. avoid/uncheck v12 full signature while generating the signed apk
Google issue: 504 is generic error that comes after app is being downloaded from google play store and before installation starts. this error code typically is being used to show the issue with google play service. but google is using this error code for non-obvious reason as well that makes user more confusing.
So advice if you are having error code: 504 while installing app from google play store use above two recipe to fix it.
This fixed 504 error for me
So at the time of generating build "Generate Signed APK -> Signature Versions: Select only V1(Jar Signature)"
I have apk on play store with with version code 5 and version name 5.0.0. But when I am trying to upload new apk to play store with version code 6 and version name 5.0.1 it showing me this error as
This configuration cannot be published for the following reason(s):
Version 5 is not served to any device configuration: all devices that might receive version 5 would receive version 6.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
I have even check out the dependency, permissions and menifest files there is no changes with old version.
I have seen though this like on the stack as well
What does this Google Play APK publish error message mean? but in may case all version code as on the store(i.e. 1-5).
Just unpublish the older one (version code 5 and version name 5.0.0) as the new version makes the older one redundant.
My app is already published.Now I wish to update it with newer version,But I did some serious changes so I wish to check it first in alpha version.
I uploaded my apk with next version in alpha,It is completely 24 hours,But still now It is not showing in playstore,In playstore my old app version is present.
I have logged in with tester-id which I have added to google-group(tester).
I am not trying to download old apk,
But trying to download the apk which I have uploaded in alpha testing.
the app which is in production have version 6.
and I uploaded version 7 in alpha testing.when I am opening the tester link with tester id,I expect it should show me my app with latest version(ie. version 7).
But still it showing version 6.
Can any one tell me how do I download it,As I am not able to find it?
I found solution, you cant find your app using search box, you can use generated direct link only.
link
I already had a version (versioncode=2) in Google Store. Yesterday after doing some changes, when I tried publishing the app, i am getting below error message and not able to publish the updates. Any idea how can I fix it?
This configuration cannot be published for the following reason(s):
Version 2 is not served to any device configuration: all devices that might receive version 2 would receive version 3.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
FYI, the new version is versioncode=3
You need to "Deactivate" the current apk in order to actually publish the new apk.
Deactivate the 2 version on the Google Play.
All this says is that version 3 is applicable for all devices that version 2 is applicable for. This means version 2 is obsolete.
If you check closely, when you upload your APK there is no option to Publish to production, only Save as Draft. This happened to me last night and drove me crazy. Now, in the morning I uploaded the new APK again and the Publish to production button was there! I don't what caused this issue but now it's fine.