app-store-compliance: The enterprise reference and automated guard that turns App Store and Google Play rejection into a designed out failure mode.
What problem it solves
App Store and Google Play rejections can leave teams searching for the cause of a brief review message, fixing it, and resubmitting. The project addresses this with documented rejection patterns, concrete fixes, pre-submission checks, and an automated guard that can run before an upload.
Key features
Pre-submission project scanning — The guard scans iOS and Android projects and reports findings before submission, with critical risks shown first and file locations included when available.
Source: README
Rejection patterns and concrete fixes — Documented rejection patterns connect store requirements to known problems and specific remediation steps, helping teams move beyond guessing at a review result.
Source: README, data
Privacy and account checks — The playbook prioritizes demo-account availability, runtime-matching privacy declarations, privacy manifests, Data safety information, and Android permissions.
Source: README
AI coding tool integration — The project installs a guard, hook configuration, and audit skill into supported AI coding tools so submission commands can be checked automatically.
Source: README, agent-os
Submission workflow integration — The guard can block known upload and submission commands when it finds a critical rejection risk, including commands used by several publishing workflows.
Source: README
Quick start
Copied verbatim from the project's README.
git clone https://github.com/mjmirza/app-store-compliance ~/repositories/app-store-compliance
bash ~/repositories/app-store-compliance/agent-os/hooks/app-store-compliance-guard.sh "/path/to/your/app"bash ~/repositories/app-store-compliance/agent-os/hooks/app-store-compliance-guard.sh /path/to/your/appWho it may suit
Inference: may suit iOS and Android developers preparing an app for submission, as well as non-developers who need a plain-English pre-submission checklist.
Topics to discuss
Which rejection patterns should the automated guard check first?
How should teams integrate the guard with their preferred AI coding tool?
Which regulatory deadlines and store-policy changes should be tracked more closely?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/mjmirza/app-store-compliance#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…