Repository navigation
|
My app was flagged or rejected on Google Play for this. System overlay permission, a tapjacking and malware signal. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Permissions and APIs (Google Play) Severity in the playbook. high What triggers it. SYSTEM_ALERT_WINDOW or application overlay declared, especially combined with AccessibilityService. What to search your code for. How to fix it. Remove overlay abuse. The overlay plus accessibility combination is a strong malware signal Google enforces against. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Permissions and APIs (Google Play)
Severity in the playbook. high
What triggers it. SYSTEM_ALERT_WINDOW or application overlay declared, especially combined with AccessibilityService.
What to search your code for.
SYSTEM_ALERT_WINDOW,TYPE_APPLICATION_OVERLAYHow to fix it. Remove overlay abuse. The overlay plus accessibility combination is a strong malware signal Google enforces against.
The guard reports this as
ANDROID-OVERLAY-TAPJACKING. The full pattern is in data/rejection-patterns.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
bash scripts/install.sh install, then run the guard…