We don't necessarily need to remove all the geofencing code, if it would be difficult to do so for some reason, but that might be the easiest way to approach this so that we can let the compiler warn us about paths by which it might be activated.
At the very least, we know that we'll need to make sure that the geofencing service is not started in response to OS boot events, and that we do not set up geofences, regardless of what the user's preference for location notifications is.
Acceptance Criteria:
The application never attempts to use the built-in Android Geofencing service, under any circumstances.
We don't necessarily need to remove all the geofencing code, if it would be difficult to do so for some reason, but that might be the easiest way to approach this so that we can let the compiler warn us about paths by which it might be activated.
At the very least, we know that we'll need to make sure that the geofencing service is not started in response to OS boot events, and that we do not set up geofences, regardless of what the user's preference for location notifications is.
Acceptance Criteria: