Tracks and Releases in Google Play - Statuses, Rollout, and Visibility
In Google Play, app publishing revolves around tracks and releases.
A track determines:
- who can see your app
- when a version becomes available
- whether Google review is required
- how to safely roll out updates
Important:
App status ≠ Release status ≠ Track status
Even a Published app can be completely unavailable to users due to track states.
Section titled “Even a Published app can be completely unavailable to users due to track states.”What is a Track in Google Play?
Section titled “What is a Track in Google Play?”A track is a distribution channel for a version of your app.
Each track:
- contains one or more releases
- has its own audience
- operates independently from other tracks
The same AAB/APK can exist in multiple tracks at once, but:
- Production always takes priority
- The version code must be unique
Main Types of Tracks
Section titled “Main Types of Tracks”🔬 Internal Testing
Section titled “🔬 Internal Testing”For
- developers
- QA
- CI/CD
Features
- up to 100 testers
- install via email or link
- no Google review
- publishing takes minutes
When to use
- automated builds
- smoke tests
- pre-release checks
🔒 Closed Testing
Section titled “🔒 Closed Testing”For
- limited group of users
- beta testers
Features
- groups by email or Google Groups
- may require review
- you can have multiple closed tracks
When to use
- staged beta
- feature-specific testing
- regional tests
🌍 Open Testing
Section titled “🌍 Open Testing”For
- all Google Play users
- but marked as “Beta”
Features
- app is publicly visible
- users opt in voluntarily
- usually requires review
When to use
- public beta testing
- collecting feedback
🚀 Production
Section titled “🚀 Production”For
- all Google Play users
Features
- full release
- always goes through review
- appears in search and recommendations
When to use
- main app release
- updates for all users
What is a Release?
Section titled “What is a Release?”A release is a specific version of your app within a track.
A release includes:
- AAB / APK
- Version code and name
- Release notes
- Rollout settings
Release Statuses
Section titled “Release Statuses”📝 Draft
Section titled “📝 Draft”- release is created but not submitted
- users cannot see it
- can be edited without restrictions
🔍 In Review
Section titled “🔍 In Review”- release is submitted for Google review
- changes are locked
- duration: from minutes to several days
✅ Active
Section titled “✅ Active”- release is available to users
- participates in Rollout
- considered the current version for the track
⏹️ Halted
Section titled “⏹️ Halted”- rollout stopped manually
- new users do not get the update
- existing users may have already updated
❌ Rejected
Section titled “❌ Rejected”- release rejected by Google
- not delivered to users
- requires fixes and a new release
Rollout and Staged Rollout
Section titled “Rollout and Staged Rollout”Full rollout
Section titled “Full rollout”- version is available to 100% of users immediately
Staged rollout
Section titled “Staged rollout”- gradual release (1%, 5%, 10%, 50%, 100%)
- can be stopped if issues arise
- available only for production
Important
- rollback is not possible
- only stop or create a new release
App Visibility
Section titled “App Visibility”| Situation | Visible to users |
|---|---|
| Internal Testing only | ❌ No |
| Active Closed Testing | ❌ No (testers only) |
| Active Open Testing | ✅ Yes (as beta) |
| Active Production Track | ✅ Yes |
| Halted Production Track | ⚠️ Partially |
| All tracks are empty | ❌ No |
Common Mistakes
Section titled “Common Mistakes”❗ App is Published but unavailable
Section titled “❗ App is Published but unavailable”- Production track is empty
- release is in Draft
- rollout = 0%
❗ Internal testing works, release does not
Section titled “❗ Internal testing works, release does not”- Internal testing does not require review
- Production almost always requires review
❗ Uploaded AAB, but no one updates
Section titled “❗ Uploaded AAB, but no one updates”- Production track is not activated
- rollout is stopped
- version is lower than current
❗ Cannot upload a new build
Section titled “❗ Cannot upload a new build”- version code is lower than previous
- version is already used in another track
CI/CD and Tracks
Section titled “CI/CD and Tracks”For automation, most often used:
- Internal testing - for auto-builds
- Production - for manual approval
Minimum service account roles:
- Release Manager
- or Custom Role with release permissions
How Tracks Relate to App Status
Section titled “How Tracks Relate to App Status”- An app can be Published but:
- Production track is empty
- Rollout is stopped
- Paused apps ignore all tracks
- Suspended apps block all releases
Conclusion
Section titled “Conclusion”Tracks are the key mechanism for safe releases in Google Play.
A good strategy:
- Internal - for CI/CD
- Closed - for verification
- Open - for feedback collection
- Production - for wide release
Understanding tracks and release statuses helps you:
- avoid publishing mistakes
- safely roll out updates
- automate releases without risk of blocks