After app hardening, the hardened app is provided in the type of a hardening package. It has to be re-signed before being released.
When re-signing a hardening package, it is recommended to employ the same keystore used for the previous signing. Otherwise, inconsistent signatures may cause failure in uploading the app to the app market.
Follow the jarsigner operating syntax:
jarsigner -digestalg SHA1 -sigalg MD5withRSA -verbose -keystore [your_keystore_path] -signedjar [signed_apk_name] [unsigned_apk_name] [your_keystore_alias]
your_keystore_pathdenotes the absolute path of the key.
signed_apk_namedenotes the name of the signed installation package.
unsigned_apk_namedenotes the name of the unsigned installation package.
your_keystore_aliasdenotes the key alias.
Right-click on the eclipse project.
Select Export, and select Export Android Application.
Click Next to confirm the operation.
Copy the path filled in the location entry, which is the absolute path of the previous keystore.
your_keystore_pathin the syntax with the copied key path.
On the Keystore page, click Next to access the Key alias selection page.
Through the Alias drop-down box, view all existing keys kept in the keystore, and select the one used in the previous app signature.
your_keystore_aliasin the syntax with the selected key alias.