How to Prevent Running on Simulators in Android & IOS Apps

Last updated March 3, 2024 by Appdome

Learn to Prevent running on simulators in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are Simulators?

Simulators are virtualized tools that are used to run software tests on mobile apps inside flexible, software-defined environments.  Hackers use simulators for malicious purposes as part of dynamic analysis efforts, where they run your mobile app in their own controlled environment to learn how your app behaves and interacts with other components or systems while it’s running.

Why Should Developers Prevent Apps from Running on Simulators?

Hackers use simulators to run mobile apps within their own controlled environment so they can mimic, observe, and study how a mobile app functions and behaves while the app is running. This lets them know how a mobile app behaves to help hackers build more effective attacks and attack methods.

For example, using simulators, hackers can observe how an app interacts with the mobile operating system, or study the methods and sequence by which the app connects to and authenticates with its backend. Simulators can also be used to observe how an application app reads/writes to the filesystem (for instance to learn if weak encryption is used, or no encryption at all).

Prerequisites for Using Prevent Running on Simulators:

To use Appdome’s mobile app security build system to Prevent running on simulators , you’ll need:

Prevent running on simulators on Mobile apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Prevent running on simulators 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. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
    4. Prevent Running on Simulators Compatible With: Obj-C, C+, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
  2. Build the feature: Prevent Running on Simulators.

    1. Building Prevent Running on Simulators by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Prevent Running on Simulators feature as shown below:
      2. fusion set that contains Prevent Running on Simulators

        Figure 1: Fusion Set that will contain the Prevent Running on Simulators 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 Prevent Running on Simulators feature via Appdome Console, to add the Prevent Running on Simulators 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 Prevent Running on Simulators feature via Appdome Console

      To build the Prevent Running on Simulators protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > ONEShield™ section.
      2. When you select the Prevent Running on Simulators you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Prevent Running on Simulators

        Fusion Set applied Prevent Running on Simulators

        Figure 4: Fusion Set that displays the newly added Prevent Running on Simulators protection

      3. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Prevent Running on Simulators protection is now added to the mobile app

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

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:

Related Articles:

To learn all of the security features included in Appdome ONEShield, visit the OneShield Knowledge Base article.

If you have any questions, please send them our way at 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.

Want a Demo?

Mobile RASP Security

GilWe're here to help
We'll get back to you in 24 hours to schedule your demo.