- Home
- Skills
- APIs & Backend
- Android Signed-Release Pipeline
Android Signed-Release Pipeline
Gradle's signing config is conditional on environment variables; with one unset it silently produces an unsigned artifact and still prints `BUILD SUCCESSFUL`.
$39
Works with the AI Agents you already use
Android Signed-Release Pipeline
Example session with this skill installed
Build the 1.4.0 release candidate of our Android app (com.example.acme, versionCode 12) with the production upload key and verify it before I upload the bundle to the internal testing track.
- Read your context and instructions
- Compiled the android signed-release pipeline
Summary
Candidate built from a clean tree at a3f9c21, signed with the recorded upload key, and verified from the artifacts. State:
verified (not submitted, not device-accepted).
| Gate | Result |
|---|---|
| Working tree | clean (git status --porcelain empty) |
| Tools | keytool 21.0.3, apksigner 35.0.0, aapt2 8.5.0 |
| Unsigned APK present | no |
apksigner verify | OK, v2 scheme, 1 signer |
| Signer SHA-256 | 7C:3E:...:9A = recorded fingerprint |
jarsigner -verify app-release.aab | jar verified |
| Package / versionCode / versionName | com.example.acme / 12 / 1.4.0 |
| debuggable | false |
| Permissions in shipped binary | INTERNET, POST_NOTIFICATIONS (allow-listed); none extra |
| Forbidden strings | none (staging\.example\.com, 10\.0\.2\.2) |
candidates/AcmeApp-1.4.0-12/
app-release.apk sha256 4b8e...d10f
app-release.aab sha256 c0a2...77e3
SHA256SUMS.txt APK-SIGNATURE.txt AAB-SIGNATURE.txt SIGNING-CERTIFICATE.txt
BUILD-INPUTS.json RELEASE-EVIDENCE.json VERIFY.txt
RELEASE-EVIDENCE.json records physicalDeviceAcceptance: "pending"; no secrets are in the folder.
Next steps
- Device acceptance on Android 10 and Android 15; record per device in
DEVICE-ACCEPTANCE.md, then flip the evidence flag. - Upload
app-release.aabto the internal testing track and writeSUBMISSION-RECEIPT.jsonwith the track, version code, upload time and console reference (statesubmitted). - Do not describe this build as "released" until the console shows published or rolling out, with the percentage.
Connects securely to your tools. The creator never sees your data.
About this skill
Gradle's signing config is conditional on environment variables; with one unset it silently produces an unsigned artifact and still prints BUILD SUCCESSFUL. This skill makes the key, the build and the verification three separate steps that read facts from files, and keeps a receipt whose states are never collapsed into "released".
Scripts
New-UploadKey.ps1: 4096-bit RSA upload key with random passwords passed to keytool only through environment variables, keystore and signing.envwritten outside the repo with owner-only ACLs, refusal to overwrite, public certificate exported as PEM with its SHA-256 fingerprint printed from the certificate itself.Build-SignedCandidate.ps1: dirty-tree guard,gradlew clean test lint bundleRelease assembleRelease, refusal if an unsigned APK appears,apksigner verify,jarsigner -verify, certificate record, a check that the APK signer digest equals the keystore certificate, SHA-256 sums,BUILD-INPUTS.jsonand a non-secretRELEASE-EVIDENCE.json.Verify-Release.ps1andverify-release.sh: read the artifacts: exactly one signer equal to the recorded fingerprint, v2 scheme, AAB JAR signature, package id, versionCode and versionName, not debuggable, only allow-listed permissions in the shipped binary (manifest merging adds library permissions), no forbidden strings (staging hosts, removed endpoints). Exit 0/1/2.
References
- The key lifecycle: owner decisions before generating, what to commit, what never to commit, rotation and recovery with and without Play App Signing, certificate fingerprint versus keystore-file hash.
- Receipt schemas: build inputs, release evidence, submission receipt.
- The state vocabulary: built, verified, device-accepted, submitted, in review, approved, published or rolling out; each with the evidence that proves it.
Requirements
Windows with Android Studio (keytool, jarsigner, apksigner, aapt2) and openssl for key generation and building; Linux, macOS or CI with the same tools for the bash verifier. No network.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Windows-first for builds. No automated Play Console uploads. Requires local Android SDK and JDK tools. Deciding Play App Signing status is a manual prerequisite.
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 19 days ago
- Software
- PowerShell 7Android StudioorJDK 17+Android SDK build-toolsOpenSSL
Git
Android Studio or the JDK provides keytool and jarsigner. The build-tools provide apksigner and aapt2.
Permissions
Shell runs keytool, gradlew, apksigner, jarsigner, aapt2, openssl and git. Read/write files: the Android project, the keystore and signing .env in a directory you choose outside the repo, and the candidate output folder. Environment variables: signing passwords are passed to keytool and Gradle only through the process environment during the run and are cleared afterwards. No network.