Repository navigation
|
How can a team catch AccessibilityService used for non accessibility purposes 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 'BIND_ACCESSIBILITY_SERVICE\|AccessibilityService' --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. BIND_ACCESSIBILITY_SERVICE declared in an app that is not an accessibility tool. The fix. Use accessibility APIs only for genuine accessibility features and declare the use, or remove the service. 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
GOOGLE-PERM-ACCESSIBILITY-MISUSEwith a coverage line and a proper exit code.What the hit means. BIND_ACCESSIBILITY_SERVICE declared in an app that is not an accessibility tool.
The fix. Use accessibility APIs only for genuine accessibility features and declare…