We are observing a regression in freeRASP v7.5.0 where legitimate, non-jailbroken devices running iOS 16.x are being flagged with a "Jailbreak" threat.
Previously, these same users were using our app integrated with freeRASP v7.3.0 without any issues. Immediately after updating the app to the version containing v7.5.0, the Talsec portal began logging these devices as jailbroken, and the RASP callbacks are being triggered on the client side.
Environment
freeRASP version: 7.5.0 (Updated from 7.3.0)
Platform: iOS
OS Version: iOS 16.x.x
Framework: Flutter v3.38.3
Observed Behavior
Devices that were previously "clean" on v7.3.0 are getting flagged as "Jailbroken" upon the first launch of app with freeRASP v7.5.0. The Talsec Portal logs confirms these detections.
For one user the issue was resolved when he completely uninstalled the app and performed a fresh installation. But for other users the issue was not resolved even after un-installing and installing the app..
Expected Behavior
The SDK should not flag non-jailbroken iOS 16 devices as compromised during a version update.