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.
Related
All of sudden google console started throwing an error message saying - "At least one of your app or app bundles contain an actions.xml file."
I have searched my entire app, there is no actions.xml.
Also used Analyze Apk tool of android studio to cross verify if any lib or other module may adding the actions.xml.
Here is one troubleshoot link from google (link) it describe the process To accept the Actions on Google Terms of Service.
But question remains the same that project doesn't contain any actions.xml.
Is it a console bug or I am missing anything.
This was very weird but when I tried to upload the apk after sometime it worked perfectly fine without any error messages.
As I rightly mentioned in the question there was no action.xml and action tag anywhere in my entire project.
It seems to be a console bug in my case.
It was a Google Play Console bug:
Thanks for your patience while our team investigated the behavior you experienced.
They have recently made some changes that should fix the problem. With the recent set of changes, please check to see if you are still experiencing the same issue. If so, I will be happy to see how else we can help.
Please ensure to clear your browser's cache and cookies first using the instructions available in our help center before accessing the Play Console again.
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
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 ....
I had updated my apk file and build a new version (upgrading the versionCode and versionName).
The files was successfully uploaded on the apk 2 days back, but still it is not updated :(
Can some one pls help me.
Its still showing "Processing update" as status on the console.
I tried un-publishing the app and re-publishing the same, it made thing even worse.
Now M unable to search my application.
Tried contacting the google guys, but still no progress.
Please help
Found a similar qstn here
My android app is not being updated on the Google Play Store
For a new app you need to have patience. It may take anything from 2 days to a week. There will be reviews and automated policy checks etc happening after which it will be available on store.
By republishing you just restarted the whole process.
Usual process may take maximum one week. Here only you can do is wait till they respond.
The chances are there the app may be rejected for the update, due to some technical reason. Keep on checking the status change. Also create a query to Google.
I have recently updated my Android app from Google Developer Console. I have updated my app from 1.1 version to 1.2 version. But how i would know that an update notification has gone to all active install user of my app.
Whether i need to write some code or is there any option available in Google Developer Console...
Please help me out , i need this essentially.
At the moment, the only way to tell is by day to day statistics from the google console to know how many have updated to your new version.
Go to statistics windows, then underneath the first graph there should be an option to display Active Installs by App Version.
Even if all your users update the app, there may be backup copies. Normally, such copies are never used, but on really rare occasions something happens and... it will be really very frustrating if the backup copies get broken in the course of time.