Publish update failed (Android PlayMarket)

Hello!
I created new android game 2 months ago and published it. But I did not create any keystore, and published with unsigned (debug) mode, as I understand, because, I didnt touch publishing setting on Player Settings!
I uploaded 3-4 updates for my app and had no problems with it, but on my next update I got this error:
"A downloaded apk or set of android app bundle was signed in debug mode. Sign the file or set in release mode".
I dont understand why I published my apk with updates for them without creating keystore, but now Google cant publish it?!

 

I'm having the same problem... seems like it could be Unity 2018.2, are you using Unity 2018.2?

 

Unity 2018.1.2f1
I published last update with this version.

 

Have the same issue. Any updates? Unity 2017.3
This issue appeared on 1 August

 

Maybe it's a Google Play issue then, as it was working fine for me in Unity 2018.1

 

Does anyone contacted with Google support about this problem?

 

I sent mail to Google's support about 3 hours ago. Waiting for answer

 

Still waiting for Google's Support response.
Meanwhile ...

First of all, check your keys in keystore file. Use keytool -list -v -keystore keystore-name.jks (no matter .jks or .keystore file extension) in the folder which contain keystore file. You'll get something like that
-----------------------------------------------------
Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

Alias name: sign
Creation date: Aug 7, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: C=US, O=Android, CN=Android Debug
Issuer: C=US, O=Android, CN=Android Debug
Serial number: 1
Valid from: Tue Jan 02 10:57:18 EET 2018 until: Thu Dec 26 10:57
Certificate fingerprints:
MD5: BLA:BLA:BLA
SHA1: BLA:BLA:BLA
SHA256: BLA:BLA:BLA
Signature algorithm name: SHA1withRSA
Subject Public Key Algorithm: 1024-bit RSA key
Version: 1
---------------------------------------------------------------------

If Owner and Issuer are equals to above - Congratulations! Your signing is Debug!

Go to Google Play Console -> Your Application -> Application Signature and match SHA from keystore and SHA from Console at Upload Cert section. They must be equal.

The problem cause by "Google Play App Signing" which you enable in console. Why so? I dont know, but it is fact. I tested that on another account where this feature was disabled. APK was uploaded succesfully.

Now about solutions. I found only two:
1 - Delete your application from console (you must fill this form https://www.google.com/googleplay/android-developer/contact/publishing, check "Delete app", send form to support and wait)
2 - Replace exist upload key with new one. Again with support's helpness. https://support.google.com/googleplay/android-developer/answer/7384423#
For both variants you must be the owner of GooglePlay Console account.

Hope, this will help someone.

 

Saw this as well:
https://forum.unity.com/threads/android-app-signing-by-google.471539/#post-3588608

 

It is the same what i wrote as second solution

 

I did not specify a key, so by default as you say it would use the Debug key, and Google used to be happy with that (at least it was in the "Closed Track" for the Alpha testing I was doing previously) But now for some reason, it's not anymore.

If I generate a key in Unity and then upload it fails and says it doesn't match the original key (which is weird because I never had a previous key)

 

Hi, I have exactly the same issue. I released a game in April on Android (using Unity 2017.something), and I let Google handle the signing.

So, I didn't touch anything in the Keystore settings in my Unity player settings, and did not generate any keystore myself.

Now, I need to upgrade my game. But when sending the new build to Google, I have the error message:
Upload failed
You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode.

But I'm building in release mode, Gradle. I really need to upgrade my production build...

 

Thank you, Anagr, your post helps me)
Guys, match MD5, SHA1 of your keystore with MD5, SHA1 in publish console. (you can find debug.keystore here: "Users\User\.android\debug.keystore"). Your keystore should be same as upload key, that means that Google Signing Center signed you app by debug key. Dont worry, your can safely reset this with Support. Before this you should to generate new key and extract it to *.pem certificate.
It helped for me!

 

You are welcome!