android-release

Automate Android release preparation by using scripts that handle version bumping, build APKs and AABs, apply zipalign to APKs, and sign packages using a JKS keystore. This outputs ready-to-publish files for GitHub and Play Console.

Yes, signing Android App Bundles for the Play Console requires a JKS keystore. The release process uses jarsigner to apply your keystore credentials to the AAB file, ensuring it meets Google Play's signing requirements.

The best way to manage versioning and output formatting is automating the version bump during the build step. This process formats outputs as named APKs for GitHub releases and signed AABs for the Play Console.

Yes, build automation scripts can perform zipalign on APKs before signing them. This ensures optimized unpacking of Android resources on the target devices prior to applying the JKS keystore signature.

Yes, the Android release process outputs both formats. It generates zipaligned and signed APK files intended for GitHub releases, alongside signed AAB files formatted specifically for Google Play Console deployment.

Your Android release workflow needs separate handling because APKs require zipalign optimization before signing, while AABs are signed directly using jarsigner. This ensures correct packaging and store compliance for both formats.