All Products
Search
Document Center

Instructions for use

Last Updated: May 24, 2022

Before you use Mobile Security Armor (MSA) to harden an APK or AAB file, ensure that the following requirements are met. To improve experience, read the following instructions before you use MSA.

  • Ensure that the content of the onCreate function for the provider can be executed multiple times. If the onCreate function contains related logic, make sure the related logic can be executed at least twice. For example, if you want to initialize a single instance in the onCreate function for the provider, you need to check whether the instance has been initialized.

  • Check the value of the minSdkVersion. Version 23 or earlier is recommended. If the value of the minSdkVersion is less than 23, MSA compresses and stores nativeLibraries in the APK file by default. If the value of the minSdkVersion of your APK or AAB file is greater than or equal to 23, MSA does not compress nativeLibraries (so) in the APK or AAB file. If you need to set the value of the minSdkVersion to a value greater than or equal to 23, you can perform one of the following operations:

    • In the application node, add android:extractNativeLibs="true".

    • Repackage the hardened APK or AAB file and set whether compression is required based on your rules.