Error 495 Play Store

[Madison Rapelyea]

Youmight receive an error that contains random numbers when you download Office apps from the Google Play store. The Google Play team is aware of this problem and is working to resolve the issues.In the meantime, please see below for more information and try the workarounds suggested.

Google Play Store Errors typically contain random numbers and are generated when you try to download apps from the Google Play Store. These errors might be due to Google Play Store updates, Google cache issues, Google Play Store stored data issues, or Google account issues.

Upload failed

You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in App Signing by Google Play, you should sign your APK or Android App Bundle with a new key before you upload it.

I'm completely stumped, as I generated a new key for this app bundle at the time of generating the app bundle, i.e. through the Build > Generate Signed Bundle / APK... menu item in Android Studio, so it is a brand new key, unused by other apps.

I've even tried creating a whole new keystore with a new key in it, but always get the same error. Is this some quirk someone else has come across?

When enrolling for App Signing by Google Play for this app, I chose the "Let Google manage and protect your app signing key (recommended)" option, and from all the documentation I've read, the key that you use to sign the app with first becomes the "Upload Key", so it seems like I'm doing everything correctly, but no dice.

I am facing the same issues, in my case signingConfig was setup, I made one simple mistake, that I forget to change app debuggable to false. so even though I generated from menu or from gradle command, build was successfully generated but it was debuggable so play store not accepting signed apk and give me and message like Upload Failed The Android Bundle was not Signed in .

Well, after a lot of screaming and shouting, including reaching out to Google Play Console support in chat (they're only first level support, so... not much help) and email (who put me in the too hard basket and said they can't offer support for app development - what? the problem is to do with uploading an app to Play Console, not app dev!), I discovered this self answered question

Basically, make sure you're doing a Clean & Rebuild Project whenever doing anything to do with signing in Android Studio. For some reason it thought my new app was using the key from my old app and kept signing with that. (I guess the solution was app development support after all!)

What happened is that you must have created another app, signed it with that keystore, and uploaded it to the Play Console, thus making it a key used to sign APKs served to end users. At the same time, you created another app which you enrolled in Play Signing: for this app, the upload certificate is extracted from the first APK you upload. Since you signed that APK with Studio as well, the same keystore was used. Play detected that it was the same certificate for both those apps, and since you used the same key for two different purposes (app signing key for your first app, and upload key for your second app), Play rejected it. The reason is that an app signing key is much more important than an upload key (the latter can be reset while the first one can't), so you shouldn't use them for two different purposes.

In other words, you'll need to create a different keystore to sign your apps enrolled in Play Signing (ideally, one per app), and make sure you never use that keystore as an app signing key for another app.

Keep in mind that this error is ambiguous and could be caused by a number of issues as visible in the other answers on this page. I had originally uploaded my app using the release build variant. Forgetting what variant I had used originally, I tried to upload the debug build variant and got this error.

The other way this can happen is if you have a signingConfig set up in the app build.gradle. It doesn't seem to matter what you specify in the signing section when you're making a bundle - even if you make a new one or choose some other keystore - it will use the one specified in the gradle file.

I had same issue with a project that has many apps and many kotlin libraries. All those apps have dependencies to those kotlin libraries, so this is reasonable configuration.When I released first app in Play Console I created keystore and one key that I used with this first app. When I tried to release second app I got this error. There was nothing bad with signing configuration. To get second app released I had to make second key to keystore and sign second apps bundle this this second key.

Error message "You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in App Signing by Google Play, you should sign your APK or Android App Bundle with a new key before you upload it." is very confusing about the situations, but advice how to fix problem was exact right, I has to create new signing key for second app.

I had the same problem. I was working on Godot Engine.The solution was to uncheck the Export with debug option while saving the .aab fileAssuming you've already put in the release.keystore with user and password in the export dialog.

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!

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.

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.

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.

- phone shut down bc it ran out of battery about 2 days ago, tried charging it on the gym treadmill, this is when the Google Play Store app crashes. A small message error pop on my screen repeatedly for a couple of seconds.

Also, I double checked that on setting I have unpicked 'automatically update', yet google play store still installed updates overnight and I had to go into settings and manually remove them again. Any idea why?

Edit 2: For anyone else having this issue with the most recent Google Update, please star the bug here so that the issue is highlighted and resolved (please let me know if there is a better place to report the bug)

What seemed to kind of fix it is to uninstall any updates on the google play store. I say kind of fixed because -despite auto update being turned off- Google Play Store updated overnight again so I had to uninstall any updates again this morning to make my phone work.

Did you manage to fix this problem? I have an S9 too with exactly the same issues. Google Play error message comes up multiple times often in quick succession every 5-10 mins of using the phone. Google maps even started giving error messages for a while. I have literally tried everything. Removing cache, clearing app data, force stopping apps, restarting, safe mode, combination of buttons which takes me to what looks like system computer code to clear the cache, deleting and adding Google accounts, removing sd card, changing time, full factory reset where I didn't restore any app data in case this was causing the issue so it was painful trying to reinstall everything (for the brief period that Google Play actually worked again). I have followed every instruction I can see online to help with this issue but nothing works. I am at my wits end. I now have an expensive phone which is fairly useless because I now can't install any apps and it is constantly producing error messages.

The error is on Google's side, after latest Play Store update (com.android.vending, Phonesky), the app is crashing. And there is not much you can do about that, because the app updates silently in background.

I have reported this bug to Google, and I hope they will fix it soon.

Yeah that's what I thought so too. I just need to police the app everyday and uninstall the updates if it quietly updates in the background overnight and then uninstall the updates lol Then the phone works again until it updates again. Will report the bug too

Check one of the replies below, the person explains it's a Google error, so the latest Play Store update (com.android.vending, Phonesky) is bad and will make the app crash. There is nothing wrong with your phone and nothing much you can do until they patch it. Try reporting the bug as well. I swear this almost seemed planned by Google haha, it was like such a good tactic to try and get me to panic buy a new phone during black friday sales! Nearly caved in too!

But yes, there's nothing more you can do other than manually uninstall the updates from google services/ play store from your phone. It WILL reinstall by itself at some point, in a day or 2, but just keep deleting the updates and you should be able to use your phone again properly.

3a8082e126