Latest updates
- DexProtector 16.1.97
- DexProtector 16.1.87
- DexProtector 16.1.83
- DexProtector 16.1.43
- DexProtector 16.1.31
Documentation
26 May 2026
DexProtector 16.1.83
This release strengthens runtime protection across Android and iOS and adds more context to security events reported to Alice.
Android:
- Strengthened runtime protection and reinforced the DexProtector Runtime Engine API against memory inspection and tampering
- Refined attestation mechanisms
- Resolved a Resource Encryption compatibility issue introduced by Android 17 QPR 1 Beta 2
iOS:
- Expanded jailbreak detection and refined attestation mechanisms
- Redesigned the crash dialog with a QR code containing Alice incident report data
- Resolved a protection issue affecting Flutter apps without CFBundleName in the main Info.plist
Alice:
- Extended diagnostic and contextual reporting, including the DexProtector version identifier on Android and iOS
More context for faster investigations
A security event is more useful when it arrives with the context needed to investigate it. This release expands reporting to Alice, adding the DexProtector version identifier on Android and iOS and correcting framework identifier reporting on iOS. For teams managing multiple applications, white-label deployments or protected SDKs, this makes it easier to identify the protection version and framework involved in an incident.
The redesigned iOS crash dialog brings that context into the support process. Alongside the app icon and configurable message, it now includes a QR code containing Alice incident report data. This gives support teams additional evidence to investigate a reported problem, reducing reliance on the user’s description alone.
For more information about DexProtector 16.1.83, or for assistance with configuration and migration, contact our technical support team at primary@licelus.com.