Repository navigation
|
How can a team catch Foreground service used for geofencing 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 -rqn 'FOREGROUND_SERVICE_LOCATION' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' . && grep -rqi 'geofenc' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' .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. Geofencing is removed as an approved foreground service use case for apps targeting API 37. An app declaring FOREGROUND_SERVICE_LOCATION whose only location use is geofencing is rejected from 27 January 2027. The fix. Move to the Geofence API (GeofencingClient) and drop FOREGROUND_SERVICE_LOCATION if geofencing was its only use. 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-FGS-GEOFENCE-REMOVEDwith a coverage line and a proper exit code.What the hit means. Geofencing is removed as an approved foregroun…