Releases: bitrise-steplib/steps-sign-apk
1.7.2
1.7.1
1.7.0
Add support for Android application has the target SDK as 30 (Android 11).
Set Enables APK Signer input to true to opt-in signin with apksigner and use APK Signature scheme and Enable debuggable APKs to control the signing process.
Thanks, @igorcferreira for contributing to this release!
1.6.0
1.5.0
When using shared libraries with native development, the 4 byte alignment may present issues. Added a new input Page alignment (page_align) which enables zipalign to apply the same page alignment to all the dependencies.
Example of step configuration:
- git::https://github.com/FutureWorkshops/steps-sign-apk@feature/zipalign_pagealign:
inputs:
- keystore_url: "$KEYSTORE_URL"
- keystore_alias: "$KEYALIAS_PASSWORD"
- keystore_password: "$KEYSTORE_PASSWORD"
- private_key_password: "$KEYALIAS_PASSWORD"
- android_app: "$BITRISE_APK_PATH_LIST"
- page_align: 'true'Migration notes
The added variable has its default value as false. So, users of the old version should see the same behavior when using the new step version.
1.4.3
1.4.2
1.4.1
Re-add the BITRISE_APK_PATH and the BITRISE_AAB_PATH output evns.
1.4.0
New outputs
BITRISE_SIGNED_APK_PATH: This output will include the path of the signed APK. If the build generates more than one APK this output will contain the last one's path.
BITRISE_SIGNED_APK_PATH_LIST: This output will include the paths of the generated APKs If multiple APKs are provided for signing the output paths are separated with | character, for example, app-armeabi-v7a-debug.apk|app-mips-debug.apk|app-x86-debug.apk
BITRISE_SIGNED_AAB_PATH: This output will include the path of the signed AAB. If the build generates more than one AAB this output will contain the last one's path.
BITRISE_SIGNED_AAB_PATH_LIST: This output will include the paths of the generated AABs. If multiple AABs are provided for signing the output paths are separated with | character.
