Parameters for Android script instrumentation
Learn more about the parameters you can use when instrumenting Android apps via script.
On this page:
Required parameters
The following table lists the available required parameters.
|
Parameter |
Description |
|---|---|
|
|
Help message with available options. |
|
|
Path to the input APK or AAB file to instrument. Verify that the file path does not include white spaces. |
|
|
The output folder. Where to place the output APK. Should be in a different place than the input APK or AAB file. |
|
|
A text file that contains a valid security token. |
|
|
Cloud URL. |
Instrumentation parameters
The following table lists the available instrumentation parameters. At least one of the instrumentation parameters must be true. If a parameter is not included, its value defaults to false.
|
Parameter |
Description |
|---|---|
|
|
Enable hybrid instrumentation (webview instrumentation). |
|
|
Enable sensor instrumentation (camera, finger print, and activity). |
|
|
Enables instrumentation of secured screens on devices running Android 12 or later. |
Optional parameters
The following table lists the available optional parameters
|
Parameter |
Description |
|---|---|
|
|
The certificate user |
|
|
The certificate password. If empty, use the certificate user. |
|
|
The key store password. |
|
|
The path to the Android certificate file. |
|
|
Set if you don't want to save the APK or AAB file in the cloud |
|
|
Force fresh instrumentation even if a cached version exists. Optionally accepts a custom label to avoid overwriting cached versions. Example: |