Input APK to be signed. The parameter accepts path to the input APK, output of the saker.apk.create() task, and the output of the saker.android.zipalign() task.

Specifies an output path for the signed APK. The output path should be forward relative. It will be used to place the signed APK in the build directory.

Specifies the SDKs (Software Development Kits) used by the task. SDKs represent development kits that are available in the build environment and to the task. They are used to find the necessary tools to perform the necessary operations. You should specify the AndroidBuildTools and AndroidPlatform SDKs so the build tasks can find the relevant tools to perform their operations. If you don't specify these SDKs, then the build tasks will attempt to locate them automatically. If they fail to do so, an exception is thrown. You can use the saker.android.sdk.buildtools() and saker.android.sdk.platform() tasks to retrieve SDKs with specific versions. The SDK names are compared in a case-insensitive way.

One or more signers to be used when signing the APK. The parameter accepts zero, one, or more signer configurations that should be used to sign the APK. If no signers are specified, or the KeyStore field for them is null, then the APK is signed using the automatically generated debug key. If more than one signer is specified, the --next-signer flag is used to separate them.