Updating app on Google Play, problem with SHA1 different from first apk file


#1

Hello,
I have problem with updating my app on Google Play Console. So, why is this happening, that my new apk SHA1 sign is different then first one that I made?
I was signing my apk using this codes:

1 keytool -genkey -v -keystore my-release-key.keystore -alias alias1 -keyalg RSA -keysize 2048 -validity 10000

2 jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore zanimljivosti.apk alias1

3 zipalign -v 4 myapp.apk myAppk.apk

I use the same keystore, with same password, everything is same except the alias names.

My question is, what causes this problem, and how to fix this. How can I have the same SHA1 parameter?


#2

I have make a mistake by using code from 1 step. So now when I get first to step 2 It works fine. So everyone who gets the same issue needs to go to step 2 for upload new app release on Google Play Console as an update.