mgravindran

@christocracy Thanks for your response. We have set stopOnTerminate as false on Android. The behaviour is working as expected when we start the plugin for location tracking. On terminate, the...

@christocracy As per docs: _If you've configured [stopOnTerminate](https://transistorsoft.github.io/capacitor-background-geolocation/interfaces/config.html#stoponterminate) false, [BackgroundGeolocation](https://transistorsoft.github.io/capacitor-background-geolocation/classes/backgroundgeolocation.html) will continue to record locations (and post them to your configured [url](https://transistorsoft.github.io/capacitor-background-geolocation/interfaces/config.html#url)) regardless of enabledHeadless: true. You should enable this...

> > it looks like the geofences are removed on TERMINATE > > No they’re not. 02-25 15:02:52.800 DEBUG [TSGeofenceManager b] ℹ️ GeofencingClient removeGeofences SUCCESS Does this log not indicate...

@christocracy - The .stop() method is called in our code in a specific scenario. It does not seem to be triggered based on the our app's logs. From the plugin...

Thanks for the clarification @christocracy. This means that there is likely a different rootcause for the geofence events not triggering. will investigate.

@christocracy Yes this log is from the production environment, hence it is set to false. On debug builds, we use the sound to debug. We are guessing that this user...

@christocracy - We also face this issue where the location error on getCurrentPosition is always undefined. Trying to simulate a permission error and the error seems undefined. Logs from the...