It’s very easy as 1 2 3.
First of all, you need to register for a publisher account.
Here’s what you will do during registration:
- Visit the Google Play Developer Console athttps://play.google.com/apps/publish/.
- Enter basic information about your developer identity — developer name, email address, and so on. You can modify this information later.
- Read and accept the Developer Distribution Agreement that applies to your country or region. Note that apps and store listings that you publish on Google Play must comply with the Developer Program Policies and US export law,
- Pay a $25 USD registration fee using Google Wallet. If you don’t have a Google Wallet account, you can quickly set one up during the process.
Then you need to set up a Google Wallet Merchant Account.
To set up a Merchant account from the Developer Console:
- Sign in to your Google Play Developer Console at https://play.google.com/apps/publish/
- Open Financial reports on the side navigation.
- Click Setup a Merchant Account now.
After finish those now you can work on registering your app.
1. On your eclipse.
Right click on your project.
Android Tools -> Export signed application package
2. Click Next
3. click browse and choose where to save and type in your Keystore name.
4. Choose whether you’re creating new Keystore (of course you choose create new keystore) or use existing Keystore. Setup your password.
5. Enter Alias, Password for Alias, Validity (50 years), First and Last name, Country Code, etc
6. Finally choose where to save your apk file.
That’s it. All you need to do now is uploading your signed apk file to Google publisher account and wait for them to be approved.
You might want to know what is Keystore and Alias.
Answer from stackoverflow
The keystore file generated by Keytool stores pairs of private and public keys. Each pair or entry stored in the keystore is refered by a unique alias. In brief:
Keystore entry = private + public key pair = identified by an alias
The keystore protects each private key with its individual password, and also protects the integrity of the entire keystore with a (possibly different) password.
For instnace, when you sign an Android application using the Export Signed Application Package option of the Eclipse Android tool, you are asked to select a keystore first, and then asked to select a single alias/entry/pair from that keystore. After providing the passwords for both the keystore and the chosen alias, the app is signed and the public key (the certificate) for that alias is embedded into the APK.
Now to answer your question, you can only release an update to an application that was signed with the alias ‘foo’ by signing the update again with the same alias. Losing the keystore where your alias is stored would prevent you from releasing an updated version of your app.
There is however a way to sign an app with a new alias, but it involves cloning an existing alias in the keystore using keytool -keyclone:
Creates a new keystore entry, which has the same private key and certificate chain as the original entry.
The original entry is identified by alias (which defaults to “mykey” if not provided). The new (destination) entry is identified by dest_alias. If no destination alias is supplied at the command line, the user is prompted for it.
If the private key password is different from the keystore password, then the entry will only be cloned if a valid keypass is supplied. This is the password used to protect the private key associated with alias. If no key password is supplied at the command line, and the private key password is different from the keystore password, the user is prompted for it. The private key in the cloned entry may be protected with a different password, if desired. If no -new option is supplied at the command line, the user is prompted for the new entry’s password (and may choose to let it be the same as for the cloned entry’s private key).
answered Apr 20 ’11 at 2:30