How to Remove Debug Information, Anti-Reversing Android & iOS Apps

Last updated August 23, 2022 by Appdome

Learn to Obfuscate Debug Information in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What is Debug Information?

Debug information is data stored inside the code of a mobile app which aids the developer in troubleshooting, tracking down issues, and fixing bugs more easily. Debug information can also be used by bad actors who want to learn how your app works by reverse engineering your code (or other malicious purposes like copying or stealing your intellectual property). Your final production app should be built in release mode (which does not contain debug information). However, more often than not, the released mobile app does contain debug information such as source code file names, line numbers, variable names and symbol names. Rather than going back to the developer and asking them to modify the app,  Appdome offers a quick and easy way to strip debug information from the Android or iOS app – instantly without code or coding.

Why Obfuscate Debug Information in Android Apps ?

Debug information in mobile apps can display information that leaves a mobile app vulnerable to attacks. Examples of the information which can be exposed are the source code file names, line numbers, variable names and symbol names to name a few. You can use Appdome to remove debug information from the logs for additional mobile app protection. 

Obfuscating Debug Information on Android apps by Using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Obfuscate Debug Information without an SDK or gateway:

  1. Upload the Mobile App to Appdome.

    1. Upload an app to Appdome’s Mobile App Security Build System

    2. Upload Method: Appdome Console or DEV-API
    3. Android Formats: .apk or .aab
  2. Build the Protection: Strip Debug Information.

    1. Building Strip Debug Information by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Strip Debug Information feature as shown below:
      2. fusion set that contains Strip Debug Information

        Figure 1: Fusion Set that will contain the Strip Debug Information feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      3. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Strip Debug Information feature via Appdome Console, to add the Strip Debug Information feature to this Fusion Set.

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Cirlce CI or other system:
        1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        2. Look for sample APIs in Appdome’s GitHub Repository
    2. Building the Strip Debug Information feature via Appdome Console

      To build the Strip Debug Information protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > Secure Communication section
      2. How: Toggle (turn ON) Strip Debug Information, as shown belowDebug Information, If needed, Customize the Threat Notification to be displayed to the mobile end-user in a standard OS dialog notification when Appdome Obfuscates . Strip Debug Information option

        Figure 3: Obfuscate Debug Information option
        Note: The App Compromise Notification contains an easy to follow default remediation path for the mobile app end user. You can customize this message as required to achieve brand specific support, workflow or other messaging.

      3. When you select the Strip Debug Information you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Strip Debug Information

        Fusion Set applied Strip Debug Information

        Figure 4: Fusion Set that displays the newly added Strip Debug Information protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Strip Debug Information protection is now added to the mobile app
  3. Certify the Strip Debug Information feature in Android Apps.

    After building Strip Debug Information, Appdome generates a Certified Secure™ certificate to guarantee that the Strip Debug Information protection has been added and is protecting the app. To verify that the Strip Debug Information protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Strip Debug Information shown in Certificate secure

    Figure 5: Certified Secure™ certificate

    Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Strip Debug Information has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Strip Debug Information and other mobile app security features are in each build of the mobile app

Prerequisites to Using Strip Debug Information:

To use Appdome’s mobile app security build system to Obfuscate Debug Information , you’ll need:

Using Appdome, there are no development or coding prerequisites to build secured Apps by using Strip Debug Information. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.

Releasing and Publishing Mobile Apps with Strip Debug Information

After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:

All apps protected by Appdome are fully compatible with any public app store, including Apple App Store, Google Play, Huawei App Gallery and more.

Protections Similar to Strip Debug Information

If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.

Have a question?

Ask an expert

NimrodMaking your security project a success!