Official Content

Specifies the key store file that will be used to sign an application that will be published in Google Play.


Platforms: Smart Devices(Android)


When you build in release mode you use your own private key to sign your application. If you don't have a private key, you can use the Keytool utility (JDK keytool utility with the -keystore parameter) to create one for you; check here for a sample. When you compile your application in release mode, the build tools use your private key along with the Jarsigner utility to sign your application's .apk file. Because the Certificate and private key you use are your own, you will have to provide the password for the keystore and key alias.

About the Android certificate

  • The Android system requires that all installed applications be digitally signed with a certificate whose private key is held by the application's developer.
  • The Android system uses the certificate as a means of identifying the author of an application and establishing trust relationships between applications.
  • The certificate is not used to control which applications the user can install.
  • The certificate does not need to be signed by a certificate authority: it is perfectly allowable, and typical, for Android applications to use self-signed certificates.



Android Specific Group

See Also

Signing Your Applications

Last update: April 2024 | © GeneXus. All rights reserved. GeneXus Powered by Globant