Repository navigation
|
My app was flagged or rejected on Google Play for this. Foreground service used for geofencing. 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. Foreground service requirements for apps targeting API 37 (Play Console Help answer 16965181) (Google Play) Severity in the playbook. high What triggers it. 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. What to search your code for. How to fix it. Move to the Geofence API (GeofencingClient) and drop FOREGROUND_SERVICE_LOCATION if geofencing was its only use. 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. Foreground service requirements for apps targeting API 37 (Play Console Help answer 16965181) (Google Play)
Severity in the playbook. high
What triggers it. 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.
What to search your code for.
FOREGROUND_SERVICE_LOCATION,geofence,GeofenceHow to fix it. Move to the Geofence API (GeofencingClient) and drop FOREGROUND_SERVICE_LOCATION if geofencing was its only use.
The guard reports this as
GOOGLE-FGS-GEOFENCE-REMOVED. The full pattern is in data/rejection-patterns.json.This …