The Play Store rejects uploads where versionCode is not strictly greater than the previously uploaded version. Use Google Play App Signing (recommended). Upload
This skill ensures your Android app meets Google Play Store requirements for a successful release. It covers essential steps like incrementing the `versionCode`, using Google Play App Signing, building the Android App Bundle (AAB), and validating store listing assets and metadata. Following this checklist helps prevent common upload rejections and optimizes your app’s delivery through Dynamic Delivery.
The skill also guides you on release tracks and staged rollouts to minimize risk during production launches, including monitoring Android Vitals metrics such as crash and ANR rates. It includes best practices for signing, ProGuard configuration, and preparing your app for review and distribution.
This skill is designed for mobile marketers managing Android app releases who need to coordinate with development and QA teams. Growth leads orchestrating staged rollouts and monitoring user impact will find it useful for setting safe release percentages and interpreting Android Vitals data. Agencies handling app store optimization (ASO) and compliance for clients can apply the checklist to ensure store listings and metadata meet Google’s policies.
First, confirm your `versionCode` increments with every build, as the Play Store rejects uploads if this isn’t strictly higher than the previous version. Next, configure signing with Google Play App Signing, uploading your app signing key to the Play Console and using a separate upload key to maintain security and recoverability.
Then, build the release AAB using Gradle to enable Dynamic Delivery, which reduces download sizes by 15-30%. Test the release build locally on devices or with bundletool to verify installation and performance before uploading. Finally, manage your release tracks by uploading to internal, closed, open, or production testing stages, applying staged rollouts starting at 5-10%, and monitoring Android Vitals metrics to catch issues early.
What happens if I don’t increment `versionCode`? The Play Store will reject your upload without processing it. Should I use APK or AAB? Always use AAB to benefit from Dynamic Delivery and smaller app sizes. How do I handle a compromised upload key? Google Play App Signing allows you to reset your upload key without affecting users.
Attach the Play Store Checklist skill to any Metaflow agent task responsible for preparing or validating Android releases. The agent will guide you through verifying version codes, signing configurations, and build outputs, as well as managing staged rollouts and monitoring critical metrics after release. This skill helps ensure your release process aligns with Play Store requirements and reduces the risk of upload rejection or user-impacting issues. We recommend pairing it with release monitoring skills to close the loop on post-launch performance.
For broader context, see our roundup of claude skills marketing, and read ultimate guide to Claude marketing skills for related setup guidance.