"Couldn't upload. Try again." error on Google Play Console

Question

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?

Answer 1

Google Chrome

Use a new Incognito window to upload the .aab or .apk (as mentioned in the comments).

Alternatively, clear the website data:

1. going to: developer console (F12) > Application > Storage > Clear site data
   • Screenshot
2. press F5 to refresh the page
3. uploading the .apk/.aab again

---

Safari

Open Preferences > Privacy > Manage Website Data > Remove All > Done

Answer 2

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.

Answer 3

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.

Answer 4

Personally what happened in my case is

I opened two gmail accounts in two tabs.One is work and other is personal.

So the upload is not working.So Close all tabs sign out completely and it worked for me.

Answer 5

As of version 119.0.6045.105 of Chrome, I can confidently say that this is about the Chrome. None of the existing suggestions worked. Then I switched to Firefox. It worked flawlessly.

Answer 6

For me, none of the mentioned solutions worked. The issue was that one of the closed testing tracks had an older APK which didn't target API 33, and the target API update duration was overdue. Make sure that all tracks are targeting at least the minimum API version specified by Google.

Answer 7

Expo users, error with app signing

For me the reason for the error on uploading was that I didn't had signed the build with the same key as my previous build version.

This happent with expo since I accidentally changed android package (bundle identifier) field in app.json to something else than my previous build (it was camel case and I lowercased it)

Answer 8

I often use Chrome to upload, but this time it happened. And I changed to Safari, working well.

Answer 9

Happened to me and tried everything from this post. Even changed the version Nothing worked. Discarded the build and created the new build in Play console and it worked.

Answer 10

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.

Answer 11

On Safari:

Preferences -> Privacy -> Manage Website Data -> Google (remove that) did it for me! ;-)

Answer 12

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.

Answer 13

I'll chime in because I had the same error. I was uploading an APK and I got the same error. My browser was Firefox. When I changed to Safari the error changed to something along the lines of: Please reduce the size of your APK to 100MB.

So I did what was needed to reduce its size below 100MB. Uploaded again and that resolved the issue in my case.

Answer 14

If you are using multiple accounts in Google Chrome, try logging into your Gmail on a separate Chrome account, and then attempt to upload the AAB file. This method worked for me:)

Answer 15

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.

Answer 16

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.

Answer 17

For me it was a VPN issue.

To solve it:

1. Go to Play Console / App Bundle Explorer
2. Push the upload button on the top of the page
3. Turn off your VPN and upload your apk or aab
4. Turn the VPN on and push Done button

Now you can add your aab to the new version

Answer 18

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.

Answer 19

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

Answer 20

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.