Just upgraded an app from V12 to V13 - text change in help only. Works fine.
Go up upload it to dev. console and it will not publish the new APK, says:
"This configuration cannot be published for the following reason(s):
Version 12 is not served to any device configuration: all devices that might receive version 12 would receive version 13."
What is it talking about? V12 was published for 40K+ devices, I've just done exactly the same thing to three other apps with no problem, but this one won't have it.
No idea what it means. All I can do is save it as draft.
I think it is known problem of Google developer console.
Please see this answer
When you upload a new version of an app, you need to manually deactivate the previous version, until you do, the dev console won't let you publish the new state.
Both answers above equally good. I had tried the second one and it didn't work. Went back a few hours later, still didn't work, did the second answer again, and it did. Very strange ....
Related
I'm trying to push an update in the Play Store and I came across the following error. I'm aware of the new target API requirement which will be in effect from November 1st, but as of now, I'm supposed to be able to push an update to play store right? If that's the case, I'm not sure why am I getting this error.
Could some one please help me?
Thank you
That's a warning, not an error. It even says "Warning" right there.
You should be able to publish it anyway. The August deadline only applies to new apps.
This warning does not (or should not) have the capacity to block your release. There are two possibilities:
your release is being blocked by some other error as well which you aren't noticing because of this warning
there is a bug in the Play Console
If it is the second option you should report it to the Play Console support team. You can contact them via the help menu in the Play Console, which is behind the "?" (Question Mark) icon. But the first option is more likely.
I contacted Google Play Store support and they told me the issue is caused because of the version code number of the app. Though I updated the version, I forgot to update the version code number.
I fixed the version code number and uploaded the APK to the play store and it worked.
Thank you
As the title says, we published a new version of an app 2 weeks ago. Play Store indicates in the registry that the new version was uploaded (1.7), and allows it to be downloaded to users who did not have it. Not so, for those who already have it, for example, users who have version 1.6, do not see the option to update, just uninstall or open.
We expected it to be only a matter of time, but 2 weeks is already too much. We contacted Google support, and they only ask us questions like: "Have automatic updates for the application enabled?" ... Does anyone know what is happening, or if it is our mistake, some step wrongly made? We generate the apk directly from Android Studio and change the version.
One of the issues that your users might have is this
Maybe they disabled the auto-updates of Google Play, but is really weird that they can't see it, maybe it's due the devices. Is your device listed as compatible with the new version of your app? Did you tried clearing Google Play cache and trying it again?
PS: Make sure you change in your Gradle (Module app) your versionCode along with the VersionName
If new users are getting the new version installed then it is definitely uploaded to the Play store correctly.
If existing users aren't seeing "update" (just open) then it means there is something about the new version of the app that is incompatible with their devices. You can check this by trying uninstalling and re-installing. If they get the old version after an uninstall / re-install (or worse, if they can't install after uninstalling) it shows that only the old version is compatible with their device.
This probably means you changed something in the manifest to make it incompatible, but that is a whole different debugging problem.
Im trying to rollout a new beta release of an android app.
I have uploaded the apk file to the Google Play console.
But in the release page I get the following warning:
While it says it is just a warning, I am unable to proceed with the rollout.
And as there are no other errors or warnings, I'm assuming the reason I cannot continue is due to this warning.
This app is only installed on 2 devices - the developers devices. The warning has no real consequences, as the app is in beta.
Is there anyone way to get passed this warning?
Same things happened to me with the version code 2. so I built and uploaded new apk with version code 3. Don't know how but it did work!
The rollout could be blocked because other parts of the app info you need to fill in are not complete.
On the left panel, make sure all the check marks are green.
This shouldn't block your rollout. If it is blocking your rollout, or something else is and the Play console isn't telling you what it is, then it is a bug in the Play Console. Please contact the Play Console support (using the Contact section under the help "?" icon) and they can check your exact details and work out what is going wrong. They can provide support using email and live chat.
It happened to me when migrated to androidx.
The numbers of affected devices for the new version was insignificant. (1 device out of 7000+)
I decided to continue with the rollout in spite of this warning.
I'm trying to update my app to the Google Play Store. I have the current version number of the app set to 2000000000 and would like to update it to 2000000001. Please don't ask my why there are such version numbers chosen.
I got this error message when I try to push the new version: "Upload failed
The version code of your APK is high and you risk not being able to update your APK.". The one thing I don't understand is that according to official google documentations the max version number is MAXINT, 2147483647, so I still have roughly 150 000 000 versions left. The other thing is, I managed to update other app with the same version numbering convention, the app is on the same dev account and I have no such error at all.
I checked all the numbers couple of times to be sure I'm not doing some stupid typo. I also already contacted Google support but maybe someone here have some kind of solution?
Google support responded to my requests. They changed the maximum available version code to 2000000000 and didn't update the documentation at the time I was posting this question (right now it is still MAXINT: 2147483647). Quite an edge case here but maybe someone will find this useful.
Looks like there was an update 08/11/2016 (UTC) in the docs. Not the old MAX_INT value or the 2000000000.
Warning: The greatest value Google Play allows for versionCode is 2100000000.
My Unity app had a high version code (not sure where from), I added version 3 and version code 3 in the Unity app, and that shut Google Play :) There is a crafty version for build.gradle though Unity 3D: What is the Android Bundle Version and Version Code and how do they relate?
So, Lately I am getting the below warning inside my developer console and to resolve the same I have done the required fixes.
As suggested by Google , here
To confirm you’ve made the correct changes, submit the updated version of your app to the Developer Console and check back after five hours. If the app hasn’t been correctly upgraded, we will display a warning.
But , if I do the same then whole of my app users will be notified and if the problem is not fixed completely then I will have to do further changes and re-upload the app to the play-store.
I was wondering , if there is any other simulation that can help me to ensure that the issue is completely fixed and then only I move forward for publishing the app.
Well , when nothing worked , then I did upload a newer version of my apk to the play-store and later on after a week I guess , the warnings were gone.
But yes you have to resolve the issue in your code and nothing else as far as the simulation concerned is present.