Command line options
- 22 Jan 2025
- 1 Minute à lire
- SombreLumière
- PDF
Command line options
- Mis à jour le 22 Jan 2025
- 1 Minute à lire
- SombreLumière
- PDF
The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article
Avez-vous trouvé ce résumé utile ?
Merci pour vos commentaires
Additional options that can be used for the Shielding Tool:
Command line options
List of command line options | |
Option | Description |
|---|---|
--help | Prints a summary of available options and exits. |
--version | Prints the Shielding Tool version number and exits. |
--display-master-key-id | Displays the unique key ID of the Shielding Tool version and exits. |
--config<config.xml> | App Shielding security configuration xml file, usually a tailored version based on config-template.xml |
--rules<rules-file> | Shielding Tool rules are loaded from this file. These rules specify how the Shielding Tool obfuscates, binds and protects the application. |
--output<path> (or -o <path>) | Output directory for generated files, or output filename for the .apk or .aab app bundle. |
--debug | Protect the application with debug mode. |
--proguard-mapping<proguard-mapping.txt> | Combines the output mapping.txt file with the specified ProGuard mapping file. |
--output-mappingmapping.txt (or -m path) | Output filename or directory for the generated mapping file. |
--disable-insight | Disable Shielding Tool diagnostics and performance telemetry collection. |
--disable-push-binding | Do not generate push bindings. This may speed up application launch time at the cost of security degradation, and should only be used if application launch is extremely slow. |
--limit-bind-class | Reduce the number of bindings per class to a minimum. |
--limit-bind-method | Reduce the number of bindings per method to a minimum. |
--check-app | Check if the given app is integrated with App Shielding. |
--arch <arch> | Comma-separated list of architectures that should be included in the final app. Supported architectures are:
If auto or nothing is specified, the Shielding Tool determines the set of included architectures by inspecting existing native libraries in the application. |
--no-arch-armeabi-v7a | Do not include App Shielding for the armeabi-v7a CPU architecture. This reduces APK size. |
--no-arch-arm64-v8a | Do not include App Shielding for the arm64-v8a CPU architecture (64-bit). This reduces APK size. |
--no-arch-x86 | Do not include App Shielding for x86 CPU architectures. This reduces APK size. |
--no-arch-x86_64 | Do not include App Shielding for the x86_64 CPU architectures (64-bit). This reduces APK size. |
--keystore <file.jks> | Sign the app using this Java keystore file (JKS file). |
--storepass <password> | JKS password (see --keystore). |
--keyname <alias> | JKS key name/alias (see --keystore). |
--keypass <password> | JKS key password, if not specified the storepass is used. (see --keystore). |
--digestalg <alg> | Cryptographic hash algorithm used when signing the app. Possible values SHA1 or SHA256 (recommended). |
--sigalg <alg> | Algorithm used for signing the app. Possible values SHA1withRSA or SHA256withRSA (recommended). |
--generate-update -config<file> (or -u <file>) | Create an App Shielding configuration file to be used for post-deployment configuration updates. For more information, see App Shielding Updatable Configuration Specification. |
Cet article vous a-t-il été utile ?