What changes
Google Play’s current policy deadlines state that geofencing is being removed as an approved foreground-service use case effective August 26, 2026, and developers can use the Geofence API for this use case.
Identify affected code
Search for long-running location foreground services used mainly to monitor entry/exit events. Separate true continuous-location features from event-based geofencing.
Reduce scope
Use the narrowest location and background behavior that genuinely supports the user-facing feature. Review permission prompts, prominent disclosures and Play Console declarations together.
Retest background behavior
After architecture changes, test on modern Android versions with battery optimization, process death and permission changes.
Update the submission story
Make sure the Play Console foreground-service declaration describes the real implementation rather than historical behavior.
Official sources
Policies and platform requirements can change. Check the linked official documentation for the latest wording before acting on a time-sensitive case.
Need case-specific help?
If your situation includes a specific warning, rejection or account state, send the exact notice rather than applying generic steps blindly.
Request assessment