I used to test migration problems via installing old APKs from google play console and then updating to the most recent internal test version.
Since at least a week this doesn't work anymore. Every share link to a specific APK just links me to the latest APK that is published. I'm talking about this share link:
So either the live production version, or as an internal tester the current internal test version.
Anyone else has this problem? I couldn't find anything about it online.
My personal fix now is to manually download the APK, install it via ADB and then update via playstore. But that's of course more annoying than just clicking a link.
I have been in contact with an agent from google for more than 1 month about this issue, first they insisted that it was not a problem, but I helped them to understand this issue with a few images. The agent who took care of me says that their technical team has been investigating this issue for a while.
It seems we have to wait until we get a proper fix. Until that, you can use this area to upload your apk and get a specific link for that:
https://play.google.com/console/u/0/internal-app-sharing
This part gave google play link for that build and still working on android devices without a problem.
Best!
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.
When I try to upload my Android App Bundle to the Google Play Console, I get this generic error message saying "Couldn't upload. Try again.".
I've already tried:
making sure my versionName and versionCode are unique among all uploaded artifacts
making sure that the .aab/.apk is signed with the proper key
re-uploading the .AAB file
re-uploading the .APK file
checking status of google services to make sure that there isn't a mass outage
asking my senior Android dev what's up
How do I resolve this error and upload my .AAB or .APK?
Google Chrome
Use a new Incognito window to upload the .aab or .apk (as mentioned in the comments).
Alternatively, clear the website data:
going to: developer console (F12) > Application > Storage > Clear site data
Screenshot
press F5 to refresh the page
uploading the .apk/.aab again
Safari
Open Preferences >
Privacy > Manage Website Data > Remove All > Done
Here's what worked for me:
After getting the error on play console. Now use 'Add from Library' option instead of 'Upload', and you will find your appbundle that failed to upload there, select it and proceed with further steps.
This problem comes out due to multiple gmail logins on same browser, if the developer account is not the default logged in account. You can solve this by signing out all gmail accounts and login in the specific gmail account.
For my case clearing data, using Incognito or changing browser did not work. So, finally I uploaded an APK file (all previous versions were AAB files) and surprisingly Google Play console accepted it!
Give a chance to APK file if the above answers are not helping you.
Do you have gmail with another account, opened in other tab? If so, sign out from both accounts, then sign in to Google Play console again.
I could simply solve the problem by usinng Firefox instead of Chrome. Nothing else helped. With Chrome the problem remained even after applying all the suggestions above. Chrome 56, OS Ubuntu 16.04
If your zip align is not successful or verification failed at the end of the zip align process, this error is likely to occur. Please analyze whether zip align was successful. Also, you can try uploading both in .apk and .aab format. You are more likely to get a more detailed error hinting a possible cause.
If you're using Unity
I was trying to upload a Unity project. Clearing browser cache, loging out of accounts, trying different browsers, zip align etc. didn't help for me. What did, was to either:
a. Upload an .apk instead of an app bundle.
For some reason, this works completely fine, but app bundles fail every time.
Sadly, apks be unavailable for new apps starting from August 2021 :(
b. Upgrade to a newer version of Unity
Versions that did not work:
2019.4.20
Versions that worked:
2020.3.3
Play Console's error message is not especially helpful, so it's difficult to say exactly what the problem was or what fixed it, but hopefully this will help someone else using Unity.
I haven't tested any Unity versions except those listed above. If you have and also have the necessary stackoverflow rights, feel free to update my list with your own findings.
On Safari:
Preferences -> Privacy -> Manage Website Data -> Google (remove that) did it for me! ;-)
After that error happened to me, I click "Add From Library" and my uploaded app bundle showed up there, and am able to select it.
No need to logout/login or clear the cache/cookies.
After All of trying above, I have just Change the browser from Chrome To "Opera" - and its uploaded very fast. It seems that opera is very fast than chrome.
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
I use the latest opentok Android SDK to development an application. My purpose is to provide a button to let user can publish / unpublish camera. It works to unpublish the camera using publisher.setPublishVideo(false); , but it doesn't work to republish when I use publisher.setPublishVideo(true);.
And I also try to use publisher.destroy() to delete the publish and recreate the publisher and then publish it, however since publisher.destroy has been called, either publisher and subscriber's video all disappear. It's very weird.
Am I using the wrong way or could anyone give me a hint?
OpenTok's Android SDK is still in beta so its has errors here and there. You have caught an error, and this error has been reported to OpenTok. Will update when this error has been resolved.
edit- This bug will be fixed in Android 1.0.1