Important to check for existing bgTask and abort, otherwise we're left with outstanding unkilled bg-tasks, resulting in ios killing the app and filing a crash-report

Uhoh, having app crashes when we try to modify current CLLocationManager settings by stopping/starting.  setConfig merely sets instance vars.  settings take effect only after the natural progression of Location events

Discovering that aggressive tracking cannot be initiated from a background push.  when started, ensure we always set isMoving: false

Introduce setter-methods for distanceFilter, stationaryRadius.  ignore calls to updateCurrentLocation when there already exists a bgTask

Implement an NSTimer to ensure we end our background-task.  Been getting app crashes referencing background job running beyond its permitted time

If BackgroundGEoLOcation is started while already in backgroudn, execute setPace immediately in order to initiate region-monitoring

Refactor ios to be more intelligent with geolocation, turning on more aggressive standard location services wehn user is detected to be moving beyond a configurable radius

Revert "Refactor to callback into javascript during sync.  Implement standard location services for background when detected to be moving, significant-changes api when stopped"

This reverts commit e0ec782d.

Refactor to callback into javascript during sync.  Implement standard location services for background when detected to be moving, significant-changes api when stopped

Android