This will create a keystore named 'clientkeystore' with the alias of 'androidclient'. During the keystore generation process, various bits of information that include a name, company, and physical location are collected. It is sealed with a password that will also need to be input in the execution of the signapk.sh script.
How to resign a .apk file:
The process to perform the task of re-signing a .apk file with a new keystore is outlined below and run from a computer running OSX:
# ./signapk.sh application.apk keystore key-pass alias
The parameters of the signapk.sh file are as follows:
parameter 1: .apk file to be signed parameter 2: keystore location parameter 3: keystore password parameter 4: key alias
The above process signs the APK with the new key.
Below is an example of signing a stock application with your own android debug key
Test Application, "test.android.application" applicaion.apk
./signapk.sh application.apk ~/Desktop/keystore changeit testapp This process creates a file named signed_application.apk in the same path as the original .apk.
The directories that have been input into the signapk.sh script for the jarsigner and zipalign executables are as follows:
Those should be the default directories (with exception to the underlined and italicized variables that should be modified to match the version of Java, User Account, and Android version.) that will need to be modified in the signapk.sh script attached to this KB Article.
In order to qualify the script for use and execute it, the following commands need to be run from the Terminal in the directory where the script is located: