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
Related
Usually the when the application gets released in the Internal Channel, the build will get reflected instantly. Within a minute.
But strangely the build is not reflected even after a day. I am using the latest new Google console which displays the status as, ('Release not live' and not 'Being Reviewed')
Can you help to understand the behavior or the cases which might cause this
This was happening to me when published an open beta version, it was the first release so in my case it was not a superseded version problem. I fixed it by completing the "Feedback URL or email address" field in the Open testing > Testers (Tab).
After doing that the status changed from "Release not live" to "Available to unlimited testers" with the green icon.
I've found it by pure luck since Play Console does not indicate where is the problem.
This usually happens when you have a production bundle/apk with a version code greater than the Internal Track's bundle/apk version code.
Check if that's the case.
I experienced the same thing. For me I had to complete the "Feedback URL or email address" field as stated above. Also in addition to that I had to go to App content and complete the Privacy Policy step. When I had declared that my app complied with Google Play Policies the status changed from "Release not live" to "Available to unlimited testers". Hope this helps someone.
I had another problem, so I summarize the both fixes.
1. Missing feedback url
Under Testing>Open testing>Testers fill the following
2. Bundle/apk version
Your bundle/apkversion code may be greater than the Internal Track's bundle/apk version code.
If it's your case, you'll have to publish a newer version.
3. Stuck on Publishing overview
If the publishing overview is set to Managed publishing on it wont be released neither.
Go under Publishing overview
Publish the content
If you do not have any version live now & this was the reason why you were using the Managed publishing
Change managed publishing to off (top right)
Go under >Setup>Advanced Settings
Select Unpublished
Warning: You can download an open testing version only if the app is published
Cheers
This can also be because you have previously paused the track.
The track needs to be resumed.
Hope this helps someone as I have stumbled upon this myself and spent some time until I noticed the track was paused (I forgot about it)
I have pushed a new version of my app.
On google developer console it is published and all old versions are unpublished but on Google Play Store it is still showing old version. I uploaded the app 2days before so it should have been updated and on developer console, it is showing as updated.
I already clear play store cached and data but still showing old app version don't know why.
I have checked, on all devices showing old versions. does anyone know why this is happening??
I had chat with google support and as per chat they have made some changes to the review process, so it may take more time to review the app thoroughly.
they also said that it usually takes a few hours and up to a few days, depends on different circumstances.
also, they provided the link for refrence
I thought to post it as an answer as if this happens with someone so this would be helpful.
I have also faced this issue. It takes some time to show your app new version on Play Store. They implement it on regional based. So don't worry it will be available in a few hours.
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.
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 ....
Android requires you to upload an APK with billing permissions through developer console to start testing real in app billing. This was straingtforward in the old developer console but in the new one, as soon as you upload an APK, it activates automatically and there is no way to de-activate.
I've seen a related question where they suggest using the old developer console but developer console does not let me use the old console because our app listing has localized content.
Update To be more clear, it lets me switch back to the old console but there is a message near my app saying
This app has localized images and/or videos, please edit in the new Developer Console.
instead of an edit button.
I've seen other people having the same issue without a solution.
Any workaround to be able to upload draft apk through the new developer console ?
In short, you can't. It seems the 'one click publish' is being advertised as a feature. They might eventually add some sort of draft support, but who knows.
Right now, it's available the option to deactivate a current published APK. At least, I was able to do it with the new Google Developer Console, one week ago.
The old developer console is accessible by either going to the top right or navigating to play.google.com/apps/publish?switch_back=1
I contacted Google. Looks like at this state there is nothing to do. Even if I delete localized store content, it wont let me use old console.
They said draft apk support is coming very soon.