name: android-release-fastlane description: Prepare and ship Android release builds with Fastlane and Gradle signing settings. Use when publishing to Play Console, configuring signing or flavors, validating R8 Proguard behavior, or preserving release artifacts like mapping files.
Android Release Fastlane
Workflow
- Validate release inputs.
Confirm
applicationId, versioning, and release notes source. Check keystore path, alias, and passwords are provided via secure local or CI secrets. - Validate Gradle release configuration.
Check
signingConfigs,buildTypes, and any product flavors. Run./gradlew :app:assembleReleaseand./gradlew :app:bundleRelease. - Verify shrinker and symbols.
Check R8 Proguard is configured as intended.
Archive
mapping.txtwith version tag for crash deobfuscation. - Validate Fastlane lane.
Inspect
fastlane/Fastfilelanes and required env vars. Run lane in dry-run style where possible before production upload. - Release readiness summary. Report artifact paths, signing identity used, and post-release checks.
Output Contract
Always include:
- Build artifacts (
.aabor.apk) and their paths. - Mapping file retention status.
- Required secrets checklist for local and CI.
- Next command to execute for release.