android - Certificate fingerprint (SHA1) should I change it with release Certificate? -


i new google play game services , managed include app. generated certificate fingerprint terminal using commant on mac test it:

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android 

my question is, when upload app dev account, should change certificate debug release? if yes, how can that?

is using same command instea of "debug.keystore" -> release.keystore ? thanks.

yes, need change it. see using androiddebugkey. when release app need sign app , use same key generate certificate.

if using android studio, can create new key store , new key alias. (build -> generate signed apk)

enter image description here

generate release certificate:

keytool -list -v -keystore ~/mypath/my.new.keystore -alias mynewalias -storepass keystorepassword -keypass aliaspassword 

edit: list certificate fingerprints (sha1, md5) using command line:

keytool -v -list -keystore yourkeystore -alias youralias  

Comments

Popular posts from this blog

javascript - Using jquery append to add option values into a select element not working -

Android soft keyboard reverts to default keyboard on orientation change -

Rendering JButton to get the JCheckBox behavior in a JTable by using images does not update my table -