Repository navigation
|
How can a team catch System overlay permission, a tapjacking and malware signal 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 'SYSTEM_ALERT_WINDOW\|TYPE_APPLICATION_OVERLAY' --include='AndroidManifest.xml' --include='*.kt' --include='*.java' .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. SYSTEM_ALERT_WINDOW or application overlay declared, especially combined with AccessibilityService. The fix. Remove overlay abuse. The overlay plus accessibility combination is a strong malware signal Google enforces against. 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
ANDROID-OVERLAY-TAPJACKINGwith a coverage line and a proper exit code.What the hit means. SYSTEM_ALERT_WINDOW or application overlay declared, especially combined with AccessibilityService.
The fix. Remove overlay abuse. The overlay plus accessibility combination…