Skip to main content

Mapping files for production builds

To enable the Kotzilla SDK to effectively handle obfuscated builds in production, it’s required to upload your mapping files. This step ensures that stack traces from release builds can be properly de-obfuscated for analysis in the Kotzilla Console.

This guide explains how to configure and run the upload task for mapping files.

Prerequisites​

To upload mapping files, ensure that the Kotzilla Gradle plugin is configured in your project. For more information on setting up the plugin, refer to the section called Update Gradle files in the get started guide.

Automatic upload (since version 1.0.1)​

Starting from version 1.0.1, the Kotzilla Gradle plugin automatically uploads your mapping files after any assembleRelease build. This means you no longer need to manually run the upload task for release builds unless you’ve turned this off.

If you prefer to disable automatic uploads (for example, in CI environments or custom build setups), you can do so by updating uploadMappingFile = false in the Kotzilla Gradle config.

Uploading mapping files using Gradle​

  1. Run the upload task from the main application module in your project. The task can be executed for a specific build flavor by running the following command:

    ./gradlew uploadMappingFile<Flavour>

  2. Example: To upload the mapping file for the release build flavour, use:

    ./gradlew uploadMappingFileRelease

Important notes​

  • When automatic upload is disabled, make sure this task is integrated into your production build process.

  • The upload task is not triggered by default in all build variants.

  • To see available upload tasks, run:

    ./gradlew tasks