Seal your app
Upload an app build to DoveRunner Console and apply runtime protection (RASP) with no code changes.
What is app sealing?
DoveRunner Mobile App Security protects a mobile app at runtime (RASP) without any code changes. You upload a finished build to DoveRunner Console, and sealing adds protections such as code encryption, anti-debugging, anti-tampering, virtual environment detection, and cheating tool detection.
Android: seal an APK or AAB
The Android sealing wizard has five steps:
- Upload file: upload the APK or AAB.
- Basic configuration: choose the app framework (Native, Unity, Flutter, React Native, and others), the sealing mode, and options such as SO encryption and Dex protection.
- Environment detection: decide whether to block or allow rooted devices, emulators, USB debugging, and similar environments.
- Tool & package detection: block macro tools, packet interception tools, keyloggers, and overlay windows.
- Advanced detection: options such as screen capture blocking and threat callbacks.
Test mode is free and shows a test message in the app, while Release mode is charged and removes it. Apply your usual ProGuard/R8 obfuscation before sealing.
Sealing invalidates the original signature, so re-sign the sealed app before installing it or submitting it to the store. The simplest way is to register your keystore under Manage KeyStore in the console, so the app is signed when you download it.
iOS: IPA sealing or SDK
- IPA sealing: upload a compiled IPA to the console. No build changes are needed, but the app has to be re-signed. It may not be enabled on every account.
- SDK sealing: register a project by Bundle ID, download the SDK, and integrate it into your build. Protection is applied on every build with your normal signing.
See the Android sealing guide and the iOS guide for details.
This lesson is a placeholder. The tutorial video is coming later.