LogoLogo
HomeArticlesCommunity ProductsPremium ProductsGitHubTalsec Website
  • 👋Introduction
  • 🛠️Integration
    • 🤖Android
      • API
      • Troubleshooting
    • 🍎iOS
      • API
      • Troubleshooting
    • 🐦Flutter
      • FlutterFlow
      • API
      • Troubleshooting
    • ⚛️React Native
      • Expo
      • API
      • Troubleshooting
    • 👾Cordova
      • API
      • Troubleshooting
    • 🪽Capacitor
      • API
      • Troubleshooting
  • 🚀Features and Pricing plans
    • The Key Differences: freeRASP vs. RASP+
  • 🎤What's New and Changelog
  • 📊Security Report
  • ⚖️User Data Policies
  • 📄License
  • 🤝Fair Usage Policy (FUP)
  • ℹ️Wiki
    • Getting Signing Certificate Hash
    • Callback Delay, Telemetry Impact, and Threat Scanning Completion Status
    • Threat detection
      • Detecting rooted or jailbroken devices
      • Emulator detection
      • Hook detection
      • App tampering detection
      • Debugger detection
      • Detecting unofficial installation
      • Device binding detection
      • Missing obfuscation detection [Android devices only]
      • Secure Hardware detection (Keystore/Keychain secure storage check)
      • Passcode
      • System VPN detection
      • Developer Mode detection [Android devices only]
      • ADB enabled detection [Android devices only]
      • Screen Capture
    • Source code obfuscation
    • isProd flag
  • 🦉FAQ
  • 🧑‍💻About Us
  • 🤝Contribution
Powered by GitBook
On this page
  • Dev vs. Release version
  • Choose the Appropriate Version to Continue Integration

Was this helpful?

Export as PDF

Integration

Last updated 13 days ago

Was this helpful?

The general flow of the integration can be decomposed into the following steps:

  1. Conforming to the prerequisites, e.g. setting up Android minSdkVersion.

  2. Adding the dependency.

  3. Setting up the configuration for the application, e.g. package name or whether it is production or not (see Dev vs. Release version).

  4. Handling the detected threats (callbacks).

  5. Starting the SDK.

  6. Enabling the source code obfuscation.

  7. Become familiar with Security Report, User Data Policies and License.

  8. Looking at , to provide an additional layer of protection by detecting malware or suspicious applications.

  9. Looking at Features and Pricing plans if you are interested in more advanced solutions to protect your application and business.

  10. Reading through Wiki and FAQ, if you are interested in more detailed information about internal workings.

Dev vs. Release version

The Dev version is intended for development purposes. It allows you to work on your app without interference from security features that could disrupt the process, e.g. if you would implement killing of the application on the debugger callback.

The Release version is meant for production and must always be used for your published app. It enables all security protections provided by freeRASP.

To configure this, set the isProd flag in freeRASP:

  • Release: isProd = true

  • Dev: isProd = false

⚠️Dev version disables some detections which won't be triggered during the development process:

  • Emulator/Simulator

  • Debugging

  • Tampering/Repackaging

  • Unofficial store/source

  • Obfuscation issues

  • Developer mode

  • ADB Enabled

Make sure that you use the Release version for the production.


Choose the Appropriate Version to Continue Integration

Choose the relevant section based on your app development platform:

🛠️
freeMalwareDetection
Cover

Android

Cover

iOS

Cover

Flutter

Cover

React Native

Cover

Cordova

Cover

Capacitor