Troubleshoot crashes that occur after you harden an Android application.
If your application runs normally before hardening but crashes on startup afterward, the hardening service may have detected a runtime risk and terminated the application. This crash can be an intended result of the hardening policy's protection mechanism.
Troubleshoot using hardening service logs
If the application crashes on startup, filter the logs and check for the following keywords:
DEFENDER
Logs with this keyword are generated by the hardening service.
behavior
The value after behavior indicates the action that was taken:
-
0: the application is closed. 1: a log is printed. 2: a pop-up window is displayed.
-
The text after the message keyword indicates the reason for the crash.
jaffer
jaffer in the logs may indicate a signature issue, such as the application being re-signed.
A "check your xxxx" message indicates that a specific risk was detected.
Troubleshoot using application crash logs
FATAL
This keyword indicates a fatal error. The subsequent stack trace provides the reason for the crash.