Perform a release-readiness review for the Android application and requested flavour/build type. If none is specified, infer candidates from Gradle files and clearly state the scope.
Inspect when present
build.gradle, build.gradle.kts, gradle.properties, settings.gradle.- Base and flavour-specific
AndroidManifest.xml.
proguard-rules.pro, consumer rules and signing/version configuration.- Source/resources containing
isOfficial, releaseDebugEnable, mappingFileUploadEnable, baseUrl, sandbox, debug, AF_STORE, Firebase, Braze or AppsFlyer configuration.
- Application IDs, app names, deep-link schemes/hosts and brand resource overrides.
Release checks
- Debug/test endpoints, logs, menus or feature flags enabled in release.
- Incorrect environment, signing, version, app ID or distribution-store metadata.
- Incorrect
AF_STORE, Firebase/Braze/AppsFlyer settings or deep-link declarations.
- Brand leakage between VT, AU, PU, UM or any detected flavour names.
- Exported components, cleartext traffic, embedded secrets or unsafe WebView/URI handling.
- Missing R8/ProGuard rules or mapping-upload risks.
Output format
Release Readiness
- Target build:
- Result: PASS / PASS WITH WARNINGS / BLOCK RELEASE
- Highest risk:
Blocking Issues
Include only genuine blockers and exact evidence.
Warnings
Include non-blocking but actionable risks.
Build Verification Checklist
Provide exact checks or commands appropriate to the detected Gradle setup.
1---2name: release-check3description: Check Android release readiness across flavours, Gradle, manifests, SDK metadata, R8 and production flags4---56Perform a release-readiness review for the Android application and requested flavour/build type. If none is specified, infer candidates from Gradle files and clearly state the scope.78## Inspect when present9- `build.gradle`, `build.gradle.kts`, `gradle.properties`, `settings.gradle`.10- Base and flavour-specific `AndroidManifest.xml`.11- `proguard-rules.pro`, consumer rules and signing/version configuration.12- Source/resources containing `isOfficial`, `releaseDebugEnable`, `mappingFileUploadEnable`, `baseUrl`, `sandbox`, `debug`, `AF_STORE`, Firebase, Braze or AppsFlyer configuration.13- Application IDs, app names, deep-link schemes/hosts and brand resource overrides.1415## Release checks16- Debug/test endpoints, logs, menus or feature flags enabled in release.17- Incorrect environment, signing, version, app ID or distribution-store metadata.18- Incorrect `AF_STORE`, Firebase/Braze/AppsFlyer settings or deep-link declarations.19- Brand leakage between VT, AU, PU, UM or any detected flavour names.20- Exported components, cleartext traffic, embedded secrets or unsafe WebView/URI handling.21- Missing R8/ProGuard rules or mapping-upload risks.2223## Output format2425# Release Readiness26- Target build:27- Result: PASS / PASS WITH WARNINGS / BLOCK RELEASE28- Highest risk:2930# Blocking Issues31Include only genuine blockers and exact evidence.3233# Warnings34Include non-blocking but actionable risks.3536# Build Verification Checklist37Provide exact checks or commands appropriate to the detected Gradle setup.
jason0404