How to Build Anti-Debugging in Android & iOS Apps

Last updated June 3, 2024 by Appdome

Learn to Block Debugging Tools in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are Debugging Tools?

All the time and effort invested in designing, developing, and testing a mobile app can be endangered if your secret information – namely, algorithms, business logic, and unique data – is stolen by extracting your design.

The discipline for extracting design from a product is called Reverse-Engineering, and has two main categories:

Static: Extracting the design of the application without running it, just inspecting its contents.
Dynamic: Extracting information about the inner workings of the application by running it in its target or controlled (emulator) environment, and using various tools to inspect the data processing of an application while it runs. This is also known as debugging.

This Knowledge Base article explains Appdome’s Anti-Debugging capabilities, a key component of ONEShield™ by Appdome, which Appdome automatically adds to every app built using Appdome.

Why Block Debugging Tools in Mobile Apps?

Debugging Tools are software tools that will allow malicious users to debug your application. Some of them are very versatile and allow you to communicate with your device and facilitate a variety of device actions including installing and debugging apps, as well as access to shell commands to run a variety of commands on a device.

Appdome’s Anti-Debugging counters and stunts malicious dynamic reverse-engineering attempts on your application.

With Block Debugging Tools, developers can achieve the following in Android:

Attempting to attach to the process with a debugger, tracing tool or code injectors will result in the application misbehaving, and eventually terminating.
Attempting to debug the Java Virtual Machine (JVM) by using JDB (or anything that utilizes the JDWP protocol) will disconnect the debugger.

in iOS, connecting with a debugger will cause the debugging client (lldb) to:

Halt.
After a sufficient wait time, the debug session will terminate and the debugger will crash.

These are the basic measures Appdome takes to make sure an attacker has to resort to other techniques such as tampering and static reversing. Both of which are protected by Appdome’s Anti-Tampering and Anti-Emulator . This three-pronged defense gives an all-around effective hardening for your mobile app.

Prerequisites for Using Anti Debugging:

To use Appdome’s mobile app security build system to Block Debugging Tools , you’ll need:

Appdome account (create a free Appdome account here)
A license for Anti Debugging
Mobile App (.ipa for iOS, or .apk or .aab for Android)
Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)

Block Debugging Tools on Mobile apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Block Debugging Tools without an SDK or gateway:

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. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
4. Anti Debugging Compatible With: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
Build the feature: Anti Debugging.
1. Building Anti Debugging by using Appdome’s DEV-API:
  1. Create and name the Fusion Set (security template) that will contain the Anti Debugging feature as shown below:
  2. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Anti Debugging feature via Appdome Console, to add the Anti Debugging feature to this Fusion Set.
  3. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set. Copy the Fusion Set ID from the Fusion Set Detail Summary (as shown below):
    
    Figure 2: Fusion Set Detail Summary
    Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).
  4. 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, Circle CI or other system:
    
    Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
    
    Look for sample APIs in Appdome’s GitHub Repository
2. Building the Anti Debugging feature via Appdome Console
  
  To build the Anti Debugging protection by using Appdome Console, follow the instructions below.
  1. Where: Inside the Appdome Console, go to Build > Security Tab > ONEShield™ section.
    Like all other options in ONEShield™, Anti Debugging is turned on by default, as shown below:
    Figure 3: Anti Debugging 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.
  2. When you select the Anti Debugging you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Anti Debugging
    
    Figure 4: Fusion Set that displays the newly added Anti Debugging protection
  3. Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Anti Debugging:
    
    Threat-Events™ OFF > In-App Defense
    If the Threat-Events™ setting is cleared (not selected). Appdome will detect and defend the user and app by enforcing Block Debugging Tools.
    
    Threat-Events™ ON > In-App Detection
    When this setting is used, Appdome detects Debugging Tools and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing, enforcement, and user notification. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Anti Debugging Intelligence and Control in Mobile Apps.
    
    Threat-Events™ ON > In-App Defense
    When this setting is used, Appdome detects and defends against Debugging Tools (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence the app’s business logic for processing. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Anti Debugging Intelligence and Control in Mobile Apps.
  4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Congratulations! The Anti Debugging protection is now added to the mobile app
Certify the Anti Debugging feature in Mobile Apps

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

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 Anti Debugging has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Anti Debugging and other mobile app security features are in each build of the mobile app

Using Threat-Events™ for Debugging Tools Intelligence and Control in Mobile Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Debugging Tools are detected. To consume and use Threat-Events™ for Debugging Tools in Mobile Apps, use AddObserverForName in Notification Center, and the code samples for Threat-Events™ for Debugging Tools shown below.

The specifications and options for Threat-Events™ for Debugging Tools are:

Threat-Event™ Elements	Block Debugging Tools Method Detail
Appdome Feature Name	Anti Debugging
Threat-Event Mode
OFF, IN-APP DEFENSE	Appdome detects, defends and notifies user (standard OS dialog) using customizable messaging.
ON, IN-APP DETECTION	Appdome detects the attack or threat and passes the event in a standard format to the app for processing (app chooses how and when to enforce).
ON, IN-APP DEFENSE	Uses Appdome Enforce mode for any attack or threat and passes the event in a standard format to the app for processing (gather intel on attacks and threats without losing any protection).
Certified Secure™ Threat Event Check
Visible in ThreatScope™
Developer Parameters for Blocking Debugging Tools Threat-Event™
Threat-Event NAME	DebuggerThreatDetected
Threat-Event DATA	reasonData
Threat-Event CODE	reasonCode
Threat-Event REF	6918
Threat-Event SCORE
currentThreatEventScore	Current Threat-Event score
threatEventsScore	Total Threat-events score

Threat-Event Context Keys
message	Message displayed for the user on event
failSafeEnforce	Timed enforcement against the identified threat
externalID	The external ID of the event which can be listened via Threat Events
osVersion	OS version of the current device
deviceModel	Current device model
deviceManufacturer	The manufacturer of the current device
fusedAppToken	The task ID of the Appdome fusion of the currently running app
kernelInfo	Info about the kernel: system name, node name, release, version and machine.
carrierPlmn	PLMN of the device. Only available for Android devices.
deviceID	Current device ID
reasonCode	Reason code of the occurred event
buildDate	Appdome fusion date of the current application
devicePlatform	OS name of the current device
carrierName	Carrier name of the current device. Only available for Android.
updatedOSVersion	Is the OS version up to date
deviceBrand	Brand of the device
deviceBoard	Board of the device
buildUser	Build user
buildHost	Build host
sdkVersion	Sdk version
timeZone	Time zone
deviceFaceDown	Is the device face down
locationLong	Location longitude conditioned by location permission
locationLat	Location latitude conditioned by location permission
locationState	Location state conditioned by location permission
wifiSsid	Wifi SSID
wifiSsidPermissionStatus	Wifi SSID permission status
threatCode	The last six characters of the threat code specify the OS, allowing the Threat Resolution Center to address the attack on the affected device.
reason	Reason for detection

With Threat-Events™ enabled (turned ON), Mobile developers can get detailed attack intelligence and granular defense control in Mobile applications and create amazing user experiences for all mobile end users when Debugging Tools are detected.

The following is a code sample for native Mobile apps, which uses all values in the specification above for Anti Debugging:

Important! Replace all placeholder instances of <Context Key> with the specific name of your threat event context key across all language examples. This is crucial to ensure your code functions correctly with the intended event data. For example, The <Context Key> could be the message, externalID, OS Version, reason code, etc.

                    IntentFilter intentFilter = new IntentFilter();
                    intentFilter.addAction("DebuggerThreatDetected");
                    BroadcastReceiver threatEventReceiver = new BroadcastReceiver() {
                        @Override
                        public void onReceive(Context context, Intent intent) {
                            String message = intent.getStringExtra("message"); // Message shown to the user
                            String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause
                            String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code
                            
                            // Current threat event score
                            String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore");
                            
                            // Total threat events score
                            String threatEventsScore = intent.getStringExtra("threatEventsScore");
                            
                            // Replace '' with your specific event context key
                            // String variable = intent.getStringExtra("");

                            // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                        }
                    };

                    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
                        registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);
                    } else {
                        registerReceiver(threatEventReceiver, intentFilter);
                    }

xxxxxxxxxx
 
IntentFilter intentFilter = new IntentFilter();
intentFilter.addAction("DebuggerThreatDetected");
BroadcastReceiver threatEventReceiver = new BroadcastReceiver() {
  @Override
  public void onReceive(Context context, Intent intent) {
    String message = intent.getStringExtra("message"); // Message shown to the user
    String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause
    String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code
​
    // Current threat event score
    String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore");
​
    // Total threat events score
    String threatEventsScore = intent.getStringExtra("threatEventsScore");
​
    // Replace '<Context Key>' with your specific event context key
    // String variable = intent.getStringExtra("<Context Key>");
​
    // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
  }
};
​
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
  registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);
} else {
  registerReceiver(threatEventReceiver, intentFilter);
}

                    val intentFilter = IntentFilter()
                    intentFilter.addAction("DebuggerThreatDetected")
                    val threatEventReceiver = object : BroadcastReceiver() {
                        override fun onReceive(context: Context?, intent: Intent?) {
                            var message = intent?.getStringExtra("message") // Message shown to the user
                            var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause
                            var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code
                            
                            // Current threat event score
                            var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore")
                            
                            // Total threat events score
                            var threatEventsScore = intent?.getStringExtra("threatEventsScore")
                            
                            // Replace '' with your specific event context key
                            // var variable = intent?.getStringExtra("")

                            // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                        }
                    }

                    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
                        registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED)
                    } else {
                        registerReceiver(threatEventReceiver, intentFilter)
                    }

xxxxxxxxxx
 
val intentFilter = IntentFilter()
intentFilter.addAction("DebuggerThreatDetected")
val threatEventReceiver = object : BroadcastReceiver() {
    override fun onReceive(context: Context?, intent: Intent?) {
        var message = intent?.getStringExtra("message") // Message shown to the user
        var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause
        var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code
          
        // Current threat event score
        var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore")
          
        // Total threat events score
        var threatEventsScore = intent?.getStringExtra("threatEventsScore")
          
        // Replace '<Context Key>' with your specific event context key
        // var variable = intent?.getStringExtra("<Context Key>")
​
        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    }
}
​
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
  registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED)
} else {
  registerReceiver(threatEventReceiver, intentFilter)
}

                    let center = NotificationCenter.default
                    center.addObserver(forName: Notification.Name("DebuggerThreatDetected"), object: nil, queue: nil) { (note) in
                        guard let usrInf = note.userInfo else {
                            return
                        }

                        let message = usrInf["message"]; // Message shown to the user
                        let reasonData = usrInf["reasonData"]; // Threat detection cause
                        let reasonCode = usrInf["reasonCode"]; // Event reason code

                        // Current threat event score
                        let currentThreatEventScore = usrInf["currentThreatEventScore"];

                        // Total threat events score
                        let threatEventsScore = usrInf["threatEventsScore"];

                        // Replace '' with your specific event context key
                        // let variable = usrInf[""];

                        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                    }

x
 
let center = NotificationCenter.default
center.addObserver(forName: Notification.Name("DebuggerThreatDetected"), object: nil, queue: nil) { (note) in
    guard let usrInf = note.userInfo else {
        return
    }
​
    let message = usrInf["message"]; // Message shown to the user
    let reasonData = usrInf["reasonData"]; // Threat detection cause
    let reasonCode = usrInf["reasonCode"]; // Event reason code
​
    // Current threat event score
    let currentThreatEventScore = usrInf["currentThreatEventScore"];
​
    // Total threat events score
    let threatEventsScore = usrInf["threatEventsScore"];
​
    // Replace '<Context Key>' with your specific event context key
    // let variable = usrInf["<Context Key>"];
​
    // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}

                    [[NSNotificationCenter defaultCenter] addObserverForName: @"DebuggerThreatDetected" object:nil queue:nil usingBlock:^(NSNotification *org_note) {
                        __block NSNotification *note = org_note;
                        dispatch_async(dispatch_get_main_queue(), ^(void) {
                            // Message shown to the user
                            NSString *message = [[note userInfo] objectForKey:@"message"];
                            
                            // Threat detection cause
                            NSString *reasonData = [[note userInfo] objectForKey:@"reasonData"];
                            
                            // Event reason code
                            NSString *reasonCode = [[note userInfo] objectForKey:@"reasonCode"];

                            // Current threat event score
                            NSString *currentThreatEventScore = [[note userInfo] objectForKey:@"currentThreatEventScore"];
                            
                            // Total threat events score
                            NSString *threatEventsScore = [[note userInfo] objectForKey:@"threatEventsScore"];
                            
                            // Replace '' with your specific event context key
                            // NSString *variable = [[note userInfo] objectForKey:@""];

                            // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                        });
                    }];

xxxxxxxxxx
 
[[NSNotificationCenter defaultCenter] addObserverForName: @"DebuggerThreatDetected" object:nil queue:nil usingBlock:^(NSNotification *org_note) {
        __block NSNotification *note = org_note;
        dispatch_async(dispatch_get_main_queue(), ^(void) {
        
        // Message shown to the user
        NSString *message = [[note userInfo] objectForKey:@"message"];
      
        // Threat detection cause
        NSString *reasonData = [[note userInfo] objectForKey:@"reasonData"];
      
        // Event reason code
        NSString *reasonCode = [[note userInfo] objectForKey:@"reasonCode"];
​
        // Current threat event score
        NSString *currentThreatEventScore = [[note userInfo]        objectForKey:@"currentThreatEventScore"];
​
        // Total threat events score
        NSString *threatEventsScore = [[note userInfo] objectForKey:@"threatEventsScore"];
​
        // Replace '<Context Key>' with your specific event context key
        // NSString *variable = [[note userInfo] objectForKey:@"<Context Key>"];
​
        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    });
}];

                const { ADDevEvents } = NativeModules;
                const aDDevEvents = new NativeEventEmitter(ADDevEvents);

                function registerToDevEvent(action, callback) {
                    NativeModules.ADDevEvents.registerForDevEvent(action);
                    aDDevEvents.addListener(action, callback);
                }

                export function registerToAllEvents() {
                    registerToDevEvent(
                        "DebuggerThreatDetected",
                        (userinfo) => Alert.alert(JSON.stringify(userinfo))

                        var message = userinfo["message"] // Message shown to the user
                        var reasonData = userinfo["reasonData"] // Threat detection cause
                        var reasonCode = userinfo["reasonCode"] // Event reason code

                        // Current threat event score
                        var currentThreatEventScore = userinfo["currentThreatEventScore"]

                        // Total threat events score
                        var threatEventsScore = userinfo["threatEventsScore"]

                        // Replace '' with your specific event context key
                        // var variable = userinfo[""]

                        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                    );
                }

xxxxxxxxxx
 
const { ADDevEvents } = NativeModules;
const aDDevEvents = new NativeEventEmitter(ADDevEvents);
​
function registerToDevEvent(action, callback) {
    NativeModules.ADDevEvents.registerForDevEvent(action);
    aDDevEvents.addListener(action, callback);
}
​
export function registerToAllEvents() {
    registerToDevEvent(
        "DebuggerThreatDetected",
        (userinfo) => Alert.alert(JSON.stringify(userinfo))
​
        var message = userinfo["message"] // Message shown to the user
        var reasonData = userinfo["reasonData"] // Threat detection cause
        var reasonCode = userinfo["reasonCode"] // Event reason code
​
        // Current threat event score
        var currentThreatEventScore = userinfo["currentThreatEventScore"]
​
        // Total threat events score
        var threatEventsScore = userinfo["threatEventsScore"]
​
        // Replace '<Context Key>' with your specific event context key
        // var variable = userinfo["<Context Key>"]
​
        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    );
}

                RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("DebuggerThreatDetected"));
                
                class ThreatEventReceiver : BroadcastReceiver
                {
                    public override void OnReceive(Context context, Intent intent)
                    {
                        String message = intent.GetStringExtra("message"); // Message shown to the user
                        String reasonData = intent.GetStringExtra("reasonData"); // Threat detection cause
                        String reasonCode = intent.GetStringExtra("reasonCode"); // Event reason code

                        // Current threat event score
                        String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore");

                        // Total threat events score
                        String threatEventsScore = intent.GetStringExtra("threatEventsScore");

                        // Replace '' with your specific event context key
                        // String variable = intent.GetStringExtra("");

                        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                    }
                }

x
 
RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("DebuggerThreatDetected"));
                
class ThreatEventReceiver : BroadcastReceiver
{
    public override void OnReceive(Context context, Intent intent)
    {
        // Message shown to the user
        String message = intent.GetStringExtra("message");
​
        // Threat detection cause
        String reasonData = intent.GetStringExtra("reasonData");
​
        // Event reason code
        String reasonCode = intent.GetStringExtra("reasonCode");
​
        // Current threat event score
        String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore");
​
        // Total threat events score
        String threatEventsScore = intent.GetStringExtra("threatEventsScore");
​
        // Replace '<Context Key>' with your specific event context key
        // String variable = intent.GetStringExtra("<Context Key>");
​
        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    }
}

                NSNotificationCenter.DefaultCenter.AddObserver(
                    (NSString)"DebuggerThreatDetected", // Threat-Event Identifier
                    delegate (NSNotification notification)
                    {
                        // Message shown to the user
                        var message = notification.UserInfo.ObjectForKey("message");
                        
                        // Threat detection cause
                        var reasonData = notification.UserInfo.ObjectForKey("reasonData");
                        
                        // Event reason code
                        var reasonCode = notification.UserInfo.ObjectForKey("reasonCode");

                        // Current threat event score
                        var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore");
                        
                        // Total threat events score
                        var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore");

                        // Replace '' with your specific event context key
                        // var variable = notification.UserInfo.ObjectForKey("");

                        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                    }
                );

x
 
NSNotificationCenter.DefaultCenter.AddObserver(
    (NSString)"DebuggerThreatDetected", // Threat-Event Identifier
    delegate (NSNotification notification)
    {
        // Message shown to the user
        var message = notification.UserInfo.ObjectForKey("message");
​
        // Threat detection cause
        var reasonData = notification.UserInfo.ObjectForKey("reasonData");
​
        // Event reason code
        var reasonCode = notification.UserInfo.ObjectForKey("reasonCode");
​
        // Current threat event score
        var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore");
​
        // Total threat events score
        var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore");
​
        // Replace '<Context Key>' with your specific event context key
        // var variable = notification.UserInfo.ObjectForKey("<Context Keys>");
​
        // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
    }
);

                window.broadcaster.addEventListener("DebuggerThreatDetected", function(userInfo) {
                    var message = userInfo.message // Message shown to the user
                    var reasonData = userInfo.reasonData // Threat detection cause
                    var reasonCode = userInfo.reasonCode // Event reason code

                    // Current threat event score
                    var currentThreatEventScore = userInfo.currentThreatEventScore

                    // Total threat events score
                    var threatEventsScore = userInfo.threatEventsScore

                    // Replace '' with your specific event context key
                    // var variable = userInfo.

                    // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                });

xxxxxxxxxx
 
window.broadcaster.addEventListener("DebuggerThreatDetected", function(userInfo) {
    var message = userInfo.message // Message shown to the user
    var reasonData = userInfo.reasonData // Threat detection cause
    var reasonCode = userInfo.reasonCode // Event reason code
​
    // Current threat event score
    var currentThreatEventScore = userInfo.currentThreatEventScore
​
    // Total threat events score
    var threatEventsScore = userInfo.threatEventsScore
​
    // Replace '<Context Key>' with your specific event context key
    // var variable = userInfo.<Context Keys>
​
    // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});

                import 'dart:async';
                import 'package:flutter/material.dart';
                import 'package:flutter/services.dart';

                class PlatformChannel extends StatefulWidget {
                    const PlatformChannel({super.key});

                    @override
                    State createState() => _PlatformChannelState();
                }

                class _PlatformChannelState extends State {
                    // Replace with your EventChannel name
                    static const String _eventChannelName = "DebuggerThreatDetected";
                    static const EventChannel _eventChannel = EventChannel(_eventChannelName);

                    @override
                    void initState() {
                        super.initState();
                        _eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError);
                    }

                    void _onEvent(Object? event) {
                        setState(() {
                            // Adapt this section based on your specific event data structure
                            var eventData = event as Map;

                            // Example: Accessing 'externalID' field from the event
                            var externalID = eventData['externalID'];

                            // Customize the rest of the fields based on your event structure
                            String message = eventData['message']; // Message shown to the user
                            String reasonData = eventData['reasonData']; // Threat detection cause
                            String reasonCode = eventData['reasonCode']; // Event reason code

                            // Current threat event score
                            String currentThreatEventScore = eventData['currentThreatEventScore'];

                            // Total threat events score
                            String threatEventsScore = eventData['threatEventsScore'];

                            // Replace '' with your specific event context key
                            // String variable = eventData[''];
                        });
                    }

                    // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
                }

x
 
import 'dart:async';
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
​
class PlatformChannel extends StatefulWidget {
    const PlatformChannel({super.key});
​
    @override
    State<PlatformChannel> createState() => _PlatformChannelState();
}
​
class _PlatformChannelState extends State<PlatformChannel> {
    // Replace with your EventChannel name
    static const String _eventChannelName = "DebuggerThreatDetected";
    static const EventChannel _eventChannel = EventChannel(_eventChannelName);
​
    @override
    void initState() {
        super.initState();
        _eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError);
    }
​
    void _onEvent(Object? event) {
        setState(() {
            // Adapt this section based on your specific event data structure
            var eventData = event as Map;
​
            // Example: Accessing 'externalID' field from the event
            var externalID = eventData['externalID'];
​
            // Customize the rest of the fields based on your event structure
            String message = eventData['message']; // Message shown to the user
            String reasonData = eventData['reasonData']; // Threat detection cause
            String reasonCode = eventData['reasonCode']; // Event reason code
​
            // Current threat event score
            String currentThreatEventScore = eventData['currentThreatEventScore'];
​
            // Total threat events score
            String threatEventsScore = eventData['threatEventsScore'];
​
            // Replace '<Context Key>' with your specific event context key
            // String variable = eventData['<Context Keys>'];
        });
    }
​
    // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}

Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Anti Debugging. 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 Anti Debugging

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:

Customizing, Configuring & Branding Secure Mobile Apps
Deploying/Publishing Secure mobile apps to Public or Private app stores
Releasing Secured Android & iOS Apps built on Appdome.

How Do I Learn More?

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.

How to Build Anti-Debugging in Android & iOS Apps

What are Debugging Tools?

Why Block Debugging Tools in Mobile Apps?

Prerequisites for Using Anti Debugging:

Block Debugging Tools on Mobile apps using Appdome

Upload the Mobile App to Appdome.

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

Build the feature: Anti Debugging.

Building Anti Debugging by using Appdome’s DEV-API:

Building the Anti Debugging feature via Appdome Console

Certify the Anti Debugging feature in Mobile Apps

Using Threat-Events™ for Debugging Tools Intelligence and Control in Mobile Apps

Related Articles:

How Do I Learn More?

Thank you!

Stop AI-Based Attacks While Automating PCI DSS 4.0 Compliance

Supercharge the Experience in Mobile App Defense

Better User Experience in Mobile Defense

Shifting Dynamics in Mobile Fraud Prevention: A Call for Developer Responsibility