We’ve made it simple to set up Proguard and Dexguard to automatically upload your mapping.txt file to de-obfuscate your crash reports. Add the following line to your ProGuard configuration file:

   -keepattributes SourceFile,LineNumberTable

If you’re using Eclipse or a build tool, check out the following sections.

Eclipse

When building for release with Eclipse, export your application to an APK using the “Export Crashlytics-enabled Android Application” exporter from the Eclipse export menu.

This exports your application using the standard ADT Android Application exporter and then uploads the ProGuard-generated mappings file to our servers.

Ant

Crashlytics extends your standard Ant tasks to manage uploading ProGuard mappings file. Quickly set up your project by following these steps. If your ant build differs significantly from those provided with the Android SDK, please refer to the comments at the top of the crashlytics_build.xml file.

Using Dexguard

Add these two lines to custom_rules.xml of dexguard.

	<property name="proguard.enabled" value="true"/>
	<import file="/dev_app/crashlytics-devtools/                  crashlytics_build.xml"/>

Maven

If you’ve already configured Maven, you’re all set. If ProGuard is configured to put the mappings file somewhere other than target/proguard_map.txt, just use this configuration option for the plugin to specify the location:

	<configuration>
   		<mapping_location>MAPPINGS_FILE_LOCATION</mapping_location>
	</configuration>

Gradle

Once Gradle is configured, ensure that minifyEnabled=true is set in any flavor you’re using Crashlytics in. Crashlytics automatically uploads the mapping files for reach of your build variants.

Using Dexguard? Just add: apply plugin: 'io.fabric' after the DexGuard and Android plugins are applied.