In Monaca, Android app has two types of build: debug version and release version. The differences between these types of build are as follows:
|Types of Build||Description||Installation|
|Debug Build||An unsigned package which cannot be distributed in the market||
|Release Build||A signed package with the developer’s code sign which can be distributed in the market||
Fill in the necessary information of your app:
|Application Name||A name representing your app publicly such as in the Market|
|Package Name||A unique name which will be used when uploading to the Android Market. It is recommended to use reverse-domain style (for example, io.monaca.app_name) for App ID. Only alphanumeric characters, periods (at least one period must be used) and underscore are allowed. Each segment should be separated by a period and started with an alphabetic character.|
|Use Different Package Name for Debug Build||If enable, the package name of the release-built and debug-built apps are different. In other words, the package name of debug-built app will have
|Version||The version number of your app. A version number consist of only number seperated by dots (for example, 1.0.0).|
|Version Code||An internal version number of your app, relative to other versions. The value must be integer, so that the applications can programmatically evaluate it for an upgrade.|
|Fullscreen||This option is only available with the Cordova 3.5 and later. If enable, your app will be run in a fullscreen mode which hide the status bar.|
Misc: various settings regarding your Android app such as:
||Specify URL(s) which can be accessed from your app. If set to
|Keep Running||Enable||Enable this if you want Cordova to keep running in the background.|
|Disallow Overscroll||Enable||Enable this if you want to disable the glow when a user scrolls beyond the edge of the webview.|
|WebView Engine||Stock WebView||Set to High Performance (Crosswalk) for a more powerful and larger app size. It’s required Android 4.0 and up. For Cordova 5.2 and and higher, Stock WebView will be applied as default.|
|Screen Orientation||Default||You can also set the device’s screen orientation when running your app as Landscape or Portrait.|
After finishing the configurations, click Save.
A keystore is a binary file that contains a set of private keys. A private key represents the entity to be identified with the app, such as a person or a company. A keystore is encrypted with a password and it cannot be restored if the password is lost. When a keystore is lost or it overwrites another keystore, it is impossible to use the same key to re-sign the signed package.
A keystore is required for the building of a release version for your Android app. In Monaca, you can either create a new keystore or import an existing one. In order to create a new keystore, please do as follows:
Android KeyStore Settings.
Then, Manage KeyStore and Alias page will appear.
Click on Clear and Generate New button. Then, the following screen will appear:
Fill in the necessary information as shown in the above screen such as:
Alias: a name representing a private key that you will use later when signing your app. Multiple aliases can be stored within one keystore.
Password: a password for the private key (alias).
Password of the keystore: a password for the keystore. You will need this password when importing this keystore.
Then, click on Generate Keystore and Alias button to Generate the keystore.
Build App for Android.
Select appropriate type of build you want and click Start Build.
If you choose
Release Build, you will also need to select an alias to sign your package before start building.
It may take several minutes for the build to complete. Please wait. Once the build is completed, your built app is ready to be installed/downloaded. See below screenshot as an example: