Environment Variables

The IITC build system uses several environment variables to override its work.

Signature of IITC Mobile release build

TRAVIS

This environment variable is automatically added when you start the build via Travis.

If (any) value is specified for variable, it gives access to specifying KEYSTORE_PASS, ALIAS_NAME and ALIAS_PASS values, which allow to specify data for IITC Mobile application signature in environment variables, and storeFile application signature key file is set to "../keystore/android.jks"

If no value is specified for a variable, the data for IITC Mobile application signature is read from the mobile/keystore.properties file.

KEYSTORE_PASS

To sign a IITC Mobile application you need to specify the storePassword parameter.

If TRAVIS environment variable is specified, then KEYSTORE_PASS from the environment variables is used, otherwise storePassword from mobile/keystore.properties.

ALIAS_NAME

To sign a IITC Mobile application you need to specify the keyAlias parameter.

If TRAVIS environment variable is specified, then ALIAS_NAME from the environment variables is used, otherwise keyAlias from mobile/keystore.properties.

ALIAS_PASS

To sign a IITC Mobile application you need to specify the keyPassword parameter.

If TRAVIS environment variable is specified, then ALIAS_PASS from the environment variables is used, otherwise keyPassword from mobile/keystore.properties.

IITC Mobile build settings

IITC_APPLICATION_ID

By default: "org.exarhteam.iitc_mobile", introduced in #361

Represents the package name used to identify your application in Google Play store and is used to build your apk’s manifest.

You can specify different applicationId for different versions of your app (flavors)

There is also an option to override via mobile/local.properties file (has less than environment variables if both are set): IITC_APPLICATION_ID="org.company.my_iitc"

IITC_MINIFY_ENABLED

Default value depends on build type, introduced in #361

minifyEnabled allows you to enable to code shrinking, obfuscation, and optimization for android application.

Code shrinking (also known as tree shaking), is the process of removing code that R8 determines is not required at runtime. This process can greatly reduce your app's size if, for example, your app includes many library dependencies but utilizes only a small part of their functionality.

There is also an option to override via mobile/local.properties file (has less than environment variables if both are set): IITC_MINIFY_ENABLED="false"