You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One verdict for the whole fleet. READY, READY_WITH_ACTIONS, NOT_CHECKED, or BLOCKED, worst app wins. Exit codes 0, 3, 1 and 2, so only a truly ready fleet exits 0.
No silent passes. The guard prints a Coverage. line before every exit naming what it scanned. A partial scan, a platform you declared but the guard did not find, a timeout, a missing or doubled summary, counts that do not match the findings, or an exit code that contradicts them is NOT_CHECKED, never READY. A waiver can never turn a partial scan into a pass.
Owner actions in the same report. Account and console steps the scan cannot see (agreements, privacy answers, Data Safety, a test on a real device) sit beside the code findings. A step set to false, or no readiness list at all, stays open.
Waivers that expire and cover one occurrence. A waiver names the app, the finding ID, its severity and its file, so it never hides the same rule firing somewhere new or at a higher severity. It needs a reason, evidence, a reviewer, and an expiry no more than 180 days out. Two waivers for the same occurrence cancel each other. An expired, incomplete, duplicated, or stale waiver is named in the report and the finding returns.
The release rules a scan cannot see. Each app declares its regions and features, and every verified, in-force Ruling Register requirement that applies blocks the app until you attest to it.
A GitHub code-scanning file. --scanning-export writes findings in the SARIF 2.1.0 format GitHub requires, so they show in the Security tab and on pull requests.
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
READY,READY_WITH_ACTIONS,NOT_CHECKED, orBLOCKED, worst app wins. Exit codes 0, 3, 1 and 2, so only a truly ready fleet exits 0.Coverage.line before every exit naming what it scanned. A partial scan, a platform you declared but the guard did not find, a timeout, a missing or doubled summary, counts that do not match the findings, or an exit code that contradicts them isNOT_CHECKED, neverREADY. A waiver can never turn a partial scan into a pass.false, or no readiness list at all, stays open.regionsandfeatures, and every verified, in-force Ruling Register requirement that applies blocks the app until you attest to it.--scanning-exportwrites findings in the SARIF 2.1.0 format GitHub requires, so they show in the Security tab and on pull requests.Source section. FLEET-SWEEP.md, What you get.
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.All reactions