storebound/tests/fixtures/scan/play-android/README.md
CRT 84ef94253c storebound scan: Google Play parity
Play rules verified against the live Policy Center / Play Console Help pages
(checked 2026-10-11, cited in cli/lib/scan/play-rules.ts): restricted
permissions and their declarations (background location, photo / video, All
files access, AccessibilityService, REQUEST_INSTALL_PACKAGES, Health Connect,
full-screen intent, VpnService), prominent disclosure and the in-app privacy
policy, Data safety vs SDK disclosures, Families (certified ad SDKs, AD_ID,
location), AD_ID on targetSdk 33+, 16 KB page sizes (Unity, React Native, NDK,
AGP, prebuilt .so), testing for new personal accounts, Play metadata, ads at
launch, payments outside Play Billing, impersonation. Detection reads manifest
components, accessibility configs, strings.xml, native toolchain versions and a
local build's merged manifest. New fixtures and tests; README table per store.
2026-10-12 00:05:35 +08:00

9 lines
732 B
Markdown

# play-android fixture
A made-up Kotlin hiking app with planted Google Play policy problems for `storebound scan` tests: background
location without a prominent disclosure, READ_MEDIA_IMAGES / READ_MEDIA_VIDEO, MANAGE_EXTERNAL_STORAGE,
REQUEST_INSTALL_PACKAGES, Health Connect permissions, an AccessibilityService without isAccessibilityTool, a
VpnService, USE_FULL_SCREEN_INTENT added by a library (only in the committed merged manifest under
app/build/intermediates), AppLovin without AD_ID in the merged manifest, an interstitial shown from the launcher
activity's onCreate, Stripe next to an in-app product, no privacy policy link in the app, and a personal developer
account created after 2023-11-13. Not a buildable project.