Step 11 - Obfuscating Android applications

Files located in the tutorial/step11-android/files directory:
allatori.xmlTypical configuration file
build.xmlSample build file


Android Studio integration is in the Step 13

Here are three steps to set up Allatori for your Android project:
1. Copy allatori.xml to your project's folder (from tutorial\step11-android\files);
2. Create allatori folder in your project's folder. Copy allatori.jar to the created folder;
3. Add the following target to your build.xml (sample build.xml is in the tutorial\step11-android\files):

    <target name="-obfuscate" unless="do.not.compile">
        <taskdef name="allatori" classname="com.allatori.ant.ObfuscatorTask" classpath="allatori/allatori.jar"/>
        <delete dir="${out.classes.absolute.dir}-obfuscated"/>
        <allatori config="allatori.xml"/>
        <property name="out.dex.input.absolute.dir" value="${out.classes.absolute.dir}-obfuscated"/>
    </target>

You may need to perform further configuration in the allatori.xml for your project. You can reference properties defined in the Ant build file from the Allatori configuration file (allatori.xml) using standard Ant syntax: ${PropertyName}.


Here is the full default build.xml with changes in bold:

<?xml version="1.0" encoding="UTF-8"?>
<project name="AllatoriIntegration" default="help">

<!-- The local.properties file is created and updated by the 'android'
     tool.
     It contains the path to the SDK. It should *NOT* be checked into
     Version Control Systems. -->
    <property file="local.properties" />

    <!-- The build.properties file can be created by you and is never touched
         by the 'android' tool. This is the place to change some of the
         default property values used by the Ant rules.
         Here are some properties you may want to change/update:

         source.dir
             The name of the source directory. Default is 'src'.
         out.dir
             The name of the output directory. Default is 'bin'.

         Properties related to the SDK location or the project target should
         be updated using the 'android' tool with the 'update' action.

         This file is an integral part of the build system for your
         application and should be checked into Version Control Systems.

         -->
    <property file="build.properties" />

    <!-- The default.properties file is created and updated by the 'android'
         tool, as well as ADT.
         This file is an integral part of the build system for your
         application and should be checked into Version Control Systems. -->
    <property file="default.properties" />


    <!-- Required pre-setup import -->
    <import file="${sdk.dir}/tools/ant/pre_setup.xml" />


<!-- extension targets. Uncomment the ones where you want to do custom work
     in between standard targets -->
<!--
    <target name="-pre-build">
    </target>
    <target name="-pre-compile">
    </target>

    [This is typically used for code obfuscation.
     Compiled code location: ${out.classes.absolute.dir}
     If this is not done in place, override ${out.dex.input.absolute.dir}]
    <target name="-post-compile">
    </target>
-->

    <target name="-obfuscate" unless="do.not.compile">
        <taskdef name="allatori" classname="com.allatori.ant.ObfuscatorTask" classpath="allatori/allatori.jar"/>
        <delete dir="${out.classes.absolute.dir}-obfuscated"/>
        <allatori config="allatori.xml"/>
        <property name="out.dex.input.absolute.dir" value="${out.classes.absolute.dir}-obfuscated"/>
    </target>

    <!-- Execute the Android Setup task that will setup some properties
         specific to the target, and import the build rules files.

         The rules file is imported from
            <SDK>/tools/ant/
         Depending on the project type it can be either:
         - main_rules.xml
         - lib_rules.xml
         - test_rules.xml

         To customize existing targets, there are two options:
         - Customize only one target:
             - copy/paste the target into this file, *before* the
               <setup> task.
             - customize it to your needs.
         - Customize the whole script.
             - copy/paste the content of the rules files (minus the top node)
               into this file, *after* the <setup> task
             - disable the import of the rules by changing the setup task
               below to <setup import="false" />.
             - customize to your needs.
    -->
    <setup />

</project>

Step 10       Step 12       Contents