Repository navigation
|
A question developers ask when shipping to the App Store and Google Play. Short, practical answer below. |
Answered by
mjmirza
Nov 7, 2026
Replies: 1 comment
|
Google reviews every active track, not just production, so an old non-compliant build in internal or closed testing can block you. Publish a compliant build to that track so it replaces the old one, or stop the track if you no longer use it, then resubmit. More detail. docs/GOOGLE-PLAY.md This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
0 replies
Answer selected by
mjmirza
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Google reviews every active track, not just production, so an old non-compliant build in internal or closed testing can block you. Publish a compliant build to that track so it replaces the old one, or stop the track if you no longer use it, then resubmit.
More detail. docs/GOOGLE-PLAY.md
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.