Migration Guide to Version 1.6.x
View product
v1.6.0
Malwarelytics for Android version 1.6.x introduces:
- a new RASP feature: runtime tampering (dynamic instrumentation) detection.
- breaking thread-safety changes to several
RaspManagermethods to fix potential ANR issues.
Summary of Config Item Changes
| Config Item in version 1.5.x | Config item in version 1.6.x |
|---|---|
| N/A | RaspConfig.runtimeTampering(DetectionConfig) |
Summary of API Changes
| Affected APIs | API Change |
|---|---|
RuntimeTamperingDetection |
Class addition |
RaspManager.isRuntimeTamperingPresent() |
Method addition |
RaspManager.getRuntimeTamperingDetection() |
Method addition |
RaspObserver.onRuntimeTamperingDetected(RuntimeTamperingDetection) |
Method addition |
RaspManager.getScreenSharingDetection() |
Thread annotation changed from @AnyThread to @WorkerThread |
RaspManager.isScreenShared() |
Thread annotation changed from @AnyThread to @WorkerThread |
RaspManager.getAndroidAutoDetection() |
Thread annotation changed from @AnyThread to @WorkerThread |
Thread Annotation Changes
The following RaspManager methods were previously annotated @AnyThread, implying they were safe to call from the main thread. This has changed - the methods must be called from a worker (background) thread now. The annotations have been corrected to @WorkerThread.
| Method | Old annotation | New annotation |
|---|---|---|
getScreenSharingDetection() |
@AnyThread |
@WorkerThread |
isScreenShared() |
@AnyThread |
@WorkerThread |
getAndroidAutoDetection() |
@AnyThread |
@WorkerThread |
If any of these methods are called on the main thread in your application, move the call to a background thread to avoid potential ANRs.
Read Next
Last updated on May 11, 2026 (11:03)
View product