After you create a security hardening task, you can view the security hardening details of the task.
Basic Information: displays the App information, including Application Name, Application Package Name, Application Version, and Application Size.
Security Hardening Package: allows you to download security hardening packages.
ImportantDuring the security hardening process, the signature information of the App is deleted. Therefore, after you download the security hardening package, you must re-sign it and then publish the re-signed security hardening package to the corresponding market.
Hardening Details: displays the comparison between before and after hardening in terms of application size, MD5, and security.
Security Hardening Classes: displays the hardened classes and the code comparison before and after the hardening.
So Files for Security Hardening: displays the so files that have been hardened.
Assets Files for Security Hardening: displays the assets files that have been hardened.
NoteWhen you create a security hardening task, if you select Classes, So Files, or Assets Files, you can view the information about Classes, So Files, and Assets Files on the Security Hardening Details page of the task.
Procedure
You can view the details of a task that is in the Hardened state. If the task is in the Hardening or Hardening Failed state, you cannot view the hardening details. The steps are as follows:
Log on to the mPaaS console and select the target App from the App list.
In the left-side navigation pane, choose Security > Mobile Security Armor > Mobile application security hardening. The Application Security Hardening page appears.
In the security hardening list, click the App name in the card of the target task to go to the Security Hardening Details page to view the hardening details.
View the classes, so files, and assets files of security hardening (optional). Move the pointer over the question mark next to Security Hardening Classes to view the code comparison before and after the security hardening.
NoteIf the decompilation fails, the code screenshots before and after the hardening will be empty.