Repository navigation
|
How can a team catch Setting non-essential cookies without prior cookie consent automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'document.cookie\|setCookie\|cookieStore\|js-cookie\|cookieConsent' --include='*.js' --include='*.ts' --include='*.html' . && ! grep -rn 'cookieBanner\|cookieConsentBanner\|acceptCookies\|cookiePreferences' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Writing to document.cookie or cookieStore without checking if the user accepted cookies via a cookie consent banner. The fix. Implement a compliant Cookie Consent banner that blocks non-essential cookies until the user gives explicit consent. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
WEB-COOKIE-CONSENTwith a coverage line and a proper exit code.What the hit means. Writing to document.cookie or cookieStore without checking if the user accepted cookies vi…