- Home
- Skills
- Mobile Development
- Android Gradle Release Check
More screenshots
Works with the AI Agents you already use
Android Gradle Release Check
This skill finds those and eleven other release-build mistakes in your Gradle files before you upload, and tells you how to fix each one.
$5
Android Gradle Release Check
Example session with this skill installed
Check this project with android-gradle-release-check.
- Read your context and instructions
- Compiled the android gradle release
$ python3 scripts/check_android_release.py examples/risky
BLOCK app/build.gradle.kts:27 A05 SECRET_IN_BUILD_CONFIG
buildConfigField("String", "PAYMENTS_API_SECRET", ""<redacted>"")
Why: A secret-named value (secret, token, password, private or API key) is written as a literal in buildConfigField, resValue or manifestPlaceholders. It is compiled into BuildConfig, the resources or the manifest of every APK, where anyone can read it with standard tools, and it sits in the repository too.
Safer: Keep server secrets on your server and give the app short-lived tokens. For keys that must ship, read them at build time from a git-ignored file or CI secret (local.properties, the Secrets Gradle Plugin, providers.gradleProperty) and restrict them on the provider side. Rotate a key that was committed.
BLOCK app/build.gradle.kts:33 A01 SIGNING_PASSWORD_IN_REPO
BLOCK app/build.gradle.kts:44 A02 RELEASE_DEBUGGABLE
BLOCK app/build.gradle.kts:47 A03 RELEASE_SIGNED_WITH_DEBUG_KEY
BLOCK app/upload-keystore.jks.base64 A06 KEYSTORE_IN_PROJECT
BLOCK gradle.properties:6 A01 SIGNING_PASSWORD_IN_REPO
BLOCK keystore.properties:2 A01 SIGNING_PASSWORD_IN_REPO
BLOCK keystore.properties:4 A01 SIGNING_PASSWORD_IN_REPO
BLOCK wear/build.gradle.kts:14 A04 TARGET_SDK_BELOW_PLAY_MINIMUM
REVIEW app/build.gradle.kts:37 A17 APK_SIGNATURE_V2_OFF
REVIEW app/build.gradle.kts:43 A11 RELEASE_NOT_OPTIMIZED
REVIEW app/build.gradle.kts:45 A13 RELEASE_NATIVE_DEBUGGABLE
REVIEW app/build.gradle.kts:53 A16 RELEASE_LINT_CHECK_OFF
REVIEW app/proguard-rules.pro:5 A15 R8_OPTIMIZATION_LIMITED
REVIEW gradle.properties:5 A15 R8_OPTIMIZATION_LIMITED
REVIEW gradle/libs.versions.toml:4 A12 TARGET_SDK_BELOW_PHONE_REQUIREMENT
REVIEW settings.gradle.kts:10 A14 NOT_READY_FOR_16KB_PAGES
REVIEW wear/build.gradle.kts:9 A14 NOT_READY_FOR_16KB_PAGES
REVIEW wear/build.gradle.kts:25 A18 RELEASE_DEBUG_KEY_PLACEHOLDER
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 8 files, 8 with Android release build content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
storePassword "..." sits in build.gradle, the release build type is still signed with signingConfigs.debug, and targetSdk = 35 no longer passes Google Play for phone apps since 31 August 2026. This skill finds those and eleven other release-build mistakes in your Gradle files before you upload, and tells you how to fix each one.
Your agent runs a scanner on build.gradle and build.gradle.kts files (app and library modules, the root build file, settings files and shared files such as Capacitor's variables.gradle), gradle.properties, local.properties, keystore.properties, key.properties and signing.properties, gradle/libs.versions.toml, R8 rule files (proguard-rules.pro, consumer-rules.pro, keepRules/*.keep) and the names of keystore files. It skips comments, follows Gradle blocks the way Gradle reads them (buildTypes { release { } }, getByName("release"), named("release"), android.buildTypes.release...), reads Kotlin DSL calls whose arguments sit on separate lines, follows simple values defined in the same file (React Native's enableProguardInReleaseBuilds, ext { targetSdkVersion = 33 }), tells Wear OS, TV, Automotive and XR modules from phone apps by their dependencies, and leaves out signing files and keystores that a .gitignore covers. It works with Android Studio, Flutter, React Native, Expo, Capacitor and Kotlin Multiplatform projects. It never runs Gradle or your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- A01: storePassword or keyPassword written in a build file (also as a fallback after System.getenv, getOrElse or orElse), signing passwords in the project's gradle.properties, and keystore.properties, key.properties, signing.properties or local.properties files with passwords that no .gitignore excludes
- A02: debuggable true or isDebuggable = true in the release build type
- A03: the release build type signed with the debug signing config, or a release signing config that points at debug.keystore (unless it is a template placeholder or the project injects its release key: see A18)
- A04: a targetSdk Google Play no longer accepts: below 34 anywhere, below 35 in Wear OS and Android Automotive OS modules, below 36 in app modules whose dependencies show a phone or tablet app
- A05: literal secrets, tokens, passwords and API keys in buildConfigField, resValue or manifestPlaceholders (keys made to ship in apps, such as Google Maps, publishable and analytics SDK keys, are not reported)
- A06: .jks or .keystore files (or base64 copies of them) in the project that no .gitignore excludes
REVIEW
- A11: R8 off for the release build of an app module: minifyEnabled false, optimization { enable = false }, or a release block that never turns it on
- A12: targetSdk 34 or 35 where the form factor cannot be seen (shared ext block, variables.gradle, gradle.properties, version catalog)
- A13: jniDebuggable true in the release build type
- A14: an Android Gradle plugin older than 8.5.1 (unless the documented legacy-packaging workaround is set) or an NDK older than r27, not ready for Google Play's 16 KB page size requirement
- A15: -dontobfuscate, -dontoptimize, -dontshrink or keep-everything rules in R8 rule files, getDefaultProguardFile("proguard-android.txt"), or android.enableR8.fullMode=false
- A16: lint checkReleaseBuilds false
- A17: APK Signature Scheme v2 turned off without v3 in a release signing config
- A18: the debug signing config on the release build type as a placeholder: the template's TODO or Caution comment is right above it (Flutter, React Native, Expo), or the project injects its release key through EAS Build or android.injected.signing
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official Android documentation link for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It reads each file as written: values set at build time, catalog accessors such as libs.versions.targetSdk, convention plugins in buildSrc or build-logic and flutter.targetSdkVersion are not followed, and product flavors, custom build types and the variant API are not treated as the release build. The form factor is read only from a module's own dependencies. AndroidManifest.xml and app source code are not read. A file git already tracks stays in the repository even after it is added to .gitignore. The target SDK and 16 KB rules follow Google Play's requirements as of November 2026. The Flutter and React Native templates sign release with the debug key; this is reported as A18 (REVIEW), because a build that does not get a release key from EAS Build, Android Studio's Generate Signed Bundle wizard or your CI is rejected by Google Play. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Static check of Gradle and properties text. Values computed at build time, convention plugins and AndroidManifest.xml are not read. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert passwords and keys (NOTREAL-...) and a text file standing in for a base64 keystore, for the scanner to find. Nothing is run.