-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ANR Java_com_aheaditec_talsec_1security_security_Natives_d #138
Comments
Getting same, here's log
Affected devices 97% Vivo
3% Nothing
OS Android 14 - 100% Version of freeRASP: 6.7.0 |
Hello @kreativityapps, @abhijeetnapses, thank you for reporting the issue. Can you send us your android package name and watcher email to Thank you. Tomas from Talsec |
This problem started happening to me too. But my IOS users also started reporting complaints. A similar situation to this error may also be happening on the IOS side. |
For me iOS users were getting false positive privileged access. Downgrade to 6.4.0 works for me! |
Hello @furkanKotic , @abhijeetnapses , could please you create the issue in the iOS repository (https://github.com/talsec/Free-RASP-iOS) and elaborate more? The last iOS SDK introduced the Dopamine jailbreak detection. Based on the data, we do not see any unexpected false positives, the current jailbreak ratio is 0,16% of devices. Kind regards, |
@msikyna few iOS users including me who got the false positive had previously used Dopamine jailbreak, then uninstalled it. Even after rebooting it was detecting a false positive. |
Hello @abhijeetnapses , rebooting does not fully remove all traces of the jailbreak. The device is "broken". If you send us an email to support@talsec.app with the exact time of the run, watcherMail, bundle id, team id, device model and os version, we can look at the data and tell you what traces have been left on the device. |
Hello, Kind regards, |
Describe the bug
I can see a huge spike in ANR's in crashlytics in production after updating freerasp from 6.6.0 to 6.7.1
To Reproduce
I can't reproduce it locally, it's only in the logs from production
Expected behavior
No ANR
Screenshots
No screenshots
Please complete the following information:
Additional context
The bug was probably introduced in 6.7.0 or 6.7.1
The text was updated successfully, but these errors were encountered: