Google says I am using the wrong keystore file.

I uploaded an app lastweek and had unity generate the keystore for me. I kept the file.
This week I wanted to do an update and I selected in Unity to use an existing keystore file. I selected the one Unity made for me last time. I hadn't made any new ones in the meantime. And when I uploaded the APK to google play it gave me an error. That the fingerprint is different and that I should use the same upload certificate.
I haven't changed anything and am using the same file to sign the app. Any ideas what I am doing wrong?
I did not lose the keystore file. I did not edit the file. It was in the same place where Unity placed it when it was build.
Am I looking at the wrong thing and is an upload certificate completely different from the keystore?

This is the first time I am using Unity for android Apps. Previously I used to make the keystores myself via the Commandline. Never had this problem with my previous app dev software.

 

Google Play Store has 2 ways of signing: one is you sign and upload app, the other is you sign with upload key and Google re-signs with the signing key that they keep. Which are you using? More Google info here.

 

Never opted into having google do it for me. I had Unity make the keystore for me this time and then you get the regular keystore questions except this time in a nice window instead of a terminal. You enter the password. tell Unity to use the created keystore file and you upload.

 

I have the same problem. Did you manage to get it working?

 

Nope. I redid the whole thing and made a "new" app.