Trying to update store listing but not able to, not able to find what's wrong with the build we haven't added anything extra in manifest file from last 3 months.
Suggested by Google play support team
Remove All Drafted Artifacts from the Developer console and then wait for 2 - 3 Hrs.
If your still not able to contact Google Console support team
After contacting support team issue resolved in 24 hrs.
For me, I had to update my Alpha and Beta builds as well.
Got the idea from Reddit: https://www.reddit.com/r/androiddev/comments/at0reb/app_removed_from_play_store_for_smscall_log/egxyr84/
Related
Couldn't find any info in the GP console or by general internet search, maybe someone has encountered this problem already.
After upgrading the target SDK levels to 29 an error started to show up when trying to review the new test build in Closed beta branch.
VALIDATE_APP_MESSAGE_TOO_MANY_LISTS_IN_TRACK
https://i.stack.imgur.com/C4gCz.png
If anyone has encountered this already, would be glad for advice on how to solve this issue.
Thanks in advance!
This error is displayed if there are too many e-mail lists for testers. You can remove the ones you don't need now, Google Play Console did not have this possibility before.
Once removed, the new build could be submitted to the closed test branch, so that solved the issue.
Cannot upload APK to google play.
Already tried other browsers and PCs. In no was it is possible to upload.
Always get:
Upload new APK to Production
Upload failed
We could not save your changes. Please try again.
Upload another APK
Seems to be something on Googles Part. A quick search shows that a lot of people is having this issue right now, me included.
EDIT 2014-03-17:
Seems like this is still a issue for a lot of people, https://code.google.com/p/android/issues/detail?id=67226
Still no word from Google though as far as I know.
EDIT 2:
Seems to work fine for me now. Not sure if it will persist or even work for others.
In my case it was telling me upload failed and to please try again.
In the network tab I could see the upload failing and retrying in a loop
I logged out and back in and I could upload the .apks
For more troubleshooting view here
https://support.google.com/googleplay/android-developer/answer/9061737?hl=en
Late answer but it might be helpful to someone.
In my case there was no problem of chrome/safari browser, After archive i got 2 apks out of which, i was uploading "xxxx-Signed.apk" so it was giving error like 'We can not save your changes. Please try again.' later i uploaded 2nd "xxxx.apk" and it uploaded successfully.
Hope helpful: My Upload failed today app currently targets API level 25 and must target at least API level 26 to ensure it is built on the latest APIs optimized for security and performance. Change your app's target API level to at least 26.
I have added in config.xml the below line then uploaded succesfully.
<preference name="android-targetSdkVersion" value="26" />
2019 Mar 13 issue occurred.
2019 Mar 13 issue got resolved.
The issue was on Google side.
This is confirmed by googleplay-developer-support#google.com
Followed the below steps:
Raised a bug here:
https://support.google.com/googleplay/android-developer/contact/publishing?extra.IssueType=submitting
They have responded. And the issue is fixed for me.
But, if you still have issue, then do the below as given by googleplay-developer-support#google.com
Raise here: https://support.google.com/accounts/answer/32050 as given by
Chat here: https://support.google.com/googleplay/android-developer/?hl=en#contact=1&topic=3450769
In my case I have uploaded the wrong apk, which was still in artifact library, So I deleted that and then upload the correct apk with the correct version it solves the problem for me.
Make sure you increased version code and still its showing same error then log out google play console and login and try again it will work 100%
Please for those who still thinking it's from google part but didn't try the cleaning solution yet, please give it a try:
This worked for me after many days of searches..
I completely uninstalled my browser (Firefox in my case)
I made sure nothing about the browser remains in my system following this ->how to completely remove firefox from ubuntu
then I re-installed the browser and logged in to my playstore console
This really worked . I'm able to upload .apk as well as .aab
I am trying to integrate Google Plus Login in my android application. When I tried running this application on android Google API emulator, I get a dialog box prompting me to update the 'Google Play Services'. On clicking 'Update' button nothing happens and I can see following error in logcat:
Can't redirect to app settings for Google Play services
I am also getting following warning in the logcat:
Google Play services out of date. Requires 3225100 but found 3158130
Also I would like to add that I had updated Google Play Services from revision 8 to revision 10.
Can anyone please tell me how to update Google Play Services on an emulator?
I know there are many questions on this topic on Stack Overflow but nothing seems to work for me. Any help would be greatly appreciated.
I'm also facing the same problem...
I had it working about 2 weeks ago (had to format, and now i am quite upset), following Chetna answer in here:
Google Play services out of date. Requires 3159100 but found 3158130
I tried to downgrade Google play services, replacing rev. 10 for 9 (rev. 9 was the version i had installed the time i got it to work - found it here: http://venomvendor.blogspot.co.il/2012/03/android-sdk-extras-by-google-inc.html), but, still no answers how to make it work! Don't understand why this question was down rated...
EDIT: So, after trying for almost a day to do this, i solved my problem (and maybe yours). There are a couple of steps to take care of this:
1) Follow Chetna answer in here (2nd answer):
Google Play services out of date. Requires 3159100 but found 3158130 (2nd answers), the gms and vending files are the most up to date that i know of.
If you don't understand what to do in step 1 =>
1.1) Go to the link above and download com.android.vending-20130716.apk and com.google.android.gms-20130716.apk.
1.2) Go to android\sdk\platform-tools and place those two files in the folder
1.3) Create AVD with android 4.2.2 (or version below) without google api and start it, then wait for it to load, till there is nothing more to load...
1.4) I only have windows so i only use this method: open command window (cmd) in that folder and do:
adb install com.android.vending-20130716.apk
and
adb install com.google.android.gms-20130716.apk
Both of these commands will take some time, and reply with a success or failure message (both replys must be success).
1.5) Turn off the AVD.
2) Just for the sake of it, downgrade your google play services to rev 9 (to do this uninstall from sdk or delete android\sdk\extras\google\google_play_services folder http://www.mediafire.com/download/bqs2kmza5vn8e04/google_play_services_9.7z - link from the venomvendor.blogspot)
3) Import android\sdk\extras\google\google_play_services\libproject\google-play-services_lib and copy it to your workspace, add it to your project through properties > add (in the library "menu")
4) Go to project > clean > clean all projects (this one did the trick for me)
It worked for me, hope it works for you too!
Cheers
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.
We have followed the instructions at http://developer.android.com/google/play/billing/billing_testing.html#billing-testing-real to introduce in-app billing to our application, and now want to add our live product IDs.
As per the instructions, we build our APK with the necessary permissions and sign the APK. Once the upload is complete, we get the following error :
"This configuration cannot be published for the following reasons : All devices that might receive version 3001 would receive version 3002."
We do NOT want to publish this APK, but only upload it as a Draft APK, in order to complete testing of IAP.
Does anyone have a workaround to this?
I was able to work around this problem by switching back to the old version of the Developer Console and then deactivating my one older version, after which I deleted that older version and saved the app. Upon returning the the new version of the Console, the problem was resolved.
However, I believe the old version of the console will soon become unavailable, so this approach may not be available much longer.
Deactivate the old version first and then you should be able to publish the new version of the app.
Switch to the old version and update the new apk...
It works for me.
Thanks Carl