Android AppSecurity 3.2.0.0
1782885930098
Hello, customer.
DoveRunner Android AppSecurity v3.2.0.0 version has been released. This update introduces React Native support, Threat Response Message Customization, Selective Dex Encryption, Selective Dex String Obfuscation, Handling Threat Detection through Callback instead of App Termination, Improvement and Fixes.
What’s New
Hybrid framework (React Native) support
From this version, our SDK supports apps built with React Native 0.79–0.85 using the Hermes JavaScript engine.
Projects using JSC (JavaScriptCore) are not supported.
Selective Dex Encryption
Encrypts specific packages to block reverse engineering at a fundamental level — a capability previously available in 2.x versions, now reintroduced in 3.2.0.0. Note that packages required for app startup are excluded from encryption by design. We recommend selective application targeting core packages that fall outside obfuscation coverage or are loaded mid-lifecycle, rather than applying it broadly across all packages.
Selective Dex String Obfuscation
The coverage of Dex string obfuscation has been significantly expanded for stronger static defense. A new Selective sub-option is also available, allowing you to target specific packages that require priority protection — helping you balance security strength with app startup performance and binary size.
Handling Threat Detection through Callback instead of App Termination
When a threat is detected, instead of automatically terminating the application, the system sends a callback (broadcast) containing threat details to your application. Since the logic to receive and process this callback must be implemented on the application side, please contact us via help center if you want to integrate callback.
Threat Response Message Customization
Customers can now directly customize certain UI elements and detection message text in the threat detection alert. (Available to authorized customers only.)
Improvements
Added tamper-protection compatibility and reinforcement options
Two new options are available to improve compatibility and strengthen integrity protection in various deployment environments (e.g., Google Play Integrity API Automatic Protection, Play Games Sidekick).
Disable File Integrity Check — Disables AppSecurity's built-in integrity check to avoid conflicts with deployment environments that modify the app's internal structure.
Signing Certificate Identity Verification — Performs additional integrity verification based on your app signing key. Can be used alongside or independently of the File Integrity Check feature.
Improved runtime performance and stability
Improved overall system stability and runtime performance. CPU usage has been reduced compared to the previous version, helping minimize any impact on app performance.
Improved DEX Obfuscation Coverage
The obfuscation scope has been expanded beyond identifiable customer packages to cover the entire app (excluding identifiable third-party libraries). When the Maximum option is selected, obfuscation is applied more aggressively than in previous versions, providing a stronger level of protection.
Detection Alert Visibility
The app no longer automatically navigates to the relevant settings screen when USB debugging or Developer Options are detected, preventing the detection alert from being immediately dismissed.
Fixed
Fixed a bug where the detection alert was not displaying correctly for certain threat types.
Fixed an issue where FamilyLink was incorrectly blocked when the work profile detection was triggered.
Fixed a bug where certain normal environments were incorrectly detected as rooted.\
Support version of OS
Android Version Support
Android 17 has been tested and confirmed supported in this release.
Please check the policy document to understand detail Android OS coverage.
React Native Version Support
0.79 ~ 0.83 Hermes engine
0.84 ~ 0.85 Hermes v1 engine
Frequently Asked Questions
You can check FAQ of 3.x versions at this help center document.
Did you like this update?
![]()
![]()
![]()
Leave your name and email so that we can reply to you (both fields are optional):
