How to sign an APK ?, APK signature?

How to sign an APK ?, APK signature?
 1. file used to generate the application Signature

① Default: debug. keystore

> The debug signature application cannot be commercially available in the Android Market. It forces you to use your own signature.
> Different computers use this file to generate different signatures. This means that if you change the machine to upgrade the apk version, the above program will not be able to overwrite the installation.

② Use eclipse to generate: xxx. keystore

③ Use AS to generate: xxx. jks

  2. Package Your Own signed APK (using android studio)  

> If no key store file exists, create

 

> Specify a file name. Note: In as, the keystore type file of the signature file is changed to a file in jks format.
> Here, the input indicates who the package name is.

 

> The above password is used to access the top path file. The top file is used to generate a signature string.
> The following Alias is an Alias. The following password is used to generate a signature and a password is required. The password may be different from the password above.
> The next 25 indicates the validity period. The google app market stipulates that the validity period of an app is no less than 25 years. It can also be changed to 100. That is to say, our xxx. jks signature file becomes invalid after January 1, 100.

> Specify the location of the generated apk. Build Type: release debug: test version.
> Click finish. Wait a moment.

> By default, the apk file generated under the bin in the As project also has a signature. Only the debug_keystore (TEST) mode is used. If we want to release it to the application market, we need to provide a signature by ourselves. We cannot use the default one, which is not suitable. As follows:

View the signature file:

 

> This is the generated apk file used to generate the signature. The above apk file already contains the signature file