已签名的发布应用包
构建并签名用于分发的 .aab
已签名的发布应用包 是 CoddyKit 上的免费 Jetpack Compose Academy 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Jetpack Compose Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Jetpack Compose Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
From Debug to Release
Your debug builds run on your device, but the Play Store needs a release build: optimized, shrunk, and cryptographically signed by you.
AAB, Not APK
The Play Store wants an Android App Bundle (.aab), not an APK. Google generates device-specific APKs from it, so users download only what they need.
What Signing Proves
A signing key proves every update truly comes from you. Android refuses to install an update signed by a different key, which protects your users.
Create an Upload Keystore
You generate a keystore file holding your key. Guard it and its passwords carefully: lose them and you can lock yourself out of updating the app.
keytool -genkey -v \
-keystore upload.jks \
-alias uploadKeep Secrets Out of Git
Never commit passwords. Put them in gradle.properties (gitignored) or environment variables and read them in your build config.
RELEASE_STORE_PASSWORD=...
RELEASE_KEY_ALIAS=uploadConfigure the signingConfig
In build.gradle you declare a signingConfig that points to the keystore and credentials, then attach it to the release build type.
signingConfigs {
create("release") { /* keystore */ }
}Shrink with R8
Turn on minifyEnabled for release. R8 removes unused code and obfuscates names, making your bundle smaller and harder to reverse engineer.
release {
isMinifyEnabled = true
}Build the Bundle
Run the bundleRelease Gradle task. It compiles, shrinks, and signs your app, producing a release .aab ready to upload.
./gradlew bundleReleaseQuick Check
You are packaging your app for the Play Store. Which artifact should you upload?
Let Google Manage Signing
With Play App Signing, Google holds the final app signing key and you keep only an upload key. If your upload key is lost, you can reset it.
Test the Release Build
Before publishing, install the signed build via an internal testing track. R8 can break reflection, so confirm everything works in the optimized variant.
Bump Your versionCode
Every upload needs a higher versionCode than the last. The Play Store rejects duplicates, so increment it on each release before you build.
versionCode = 2
versionName = "1.1"Recap: Ready to Upload
You created a keystore, set up a signingConfig, shrank with R8, and built a signed .aab. Your app is ready for the Play Console.
常见问题解答
「已签名的发布应用包」课时是免费的吗？
是的 — 「已签名的发布应用包」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Jetpack Compose Academy 课程的其余内容，请升级到 CoddyKit PRO。 Jetpack Compose Academy 课程共包含 4 节课。
「已签名的发布应用包」这节课中我会学到什么？
构建并签名用于分发的 .aab 你通过在浏览器中直接运行的动手代码来练习 Jetpack Compose Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Jetpack Compose Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Jetpack Compose Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「已签名的发布应用包」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Jetpack Compose Academy 课中编写并运行代码吗？
能。每节 Jetpack Compose Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。