Fix Android bugs with dynamically setting locationTemplate/geofenceTemplate. Fix Android bug revoking location permission with startGeofences mode. Fix iOS threading issue with HTTP service and batchSync

Author: christocracy

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Change Log
 
+## [2.14.2] 2018-11-20
+- [Added] Android SDK 28 requires new permission to use foreground-service.
+- [Fixed] Do not calculate odometer with geofence events.  Android geofence event's location timestamp does not correspond with the actual time the geofence fires since Android is performing some heuristics in the background to ensure the potential geofence event is not a false positive.  The actual geofence event can fire some minutes in the future (ie: the location timestamp will be some minutues in the past).  Using geofence location in odometer calculations will corrupt the odometer value.
+- [Fixed] Android could not dynamically update the `locationTemplate` / `geofenceTemplate` without `#stop` and application restart.
+- [Fixed] Android `startGeofences` after revoking & re-granting permission would fail to launch the plugin's Service.
+- [Fixed] iOS HTTP crash when using `batchSync: true`.  At application boot, there was a threading issue if the server returned an HTTP error, multiple instances of the HTTP service could run, causing a crash.
+
 ## [2.14.1] 2018-10-29
 - [Fixed] react-native link on Windows.
 

android/libs/com/transistorsoft/tslocationmanager/2.14.1/tslocationmanager-2.14.1.aar

@@ -0,0 +1 @@
+5cd37c32fff77bba65680cad4625d7fd

android/libs/com/transistorsoft/tslocationmanager/2.14.1/tslocationmanager-2.14.1.aar.md5

@@ -0,0 +1 @@
+c5c2919289eeea03d4a3d8064241d199eb0670f2

android/libs/com/transistorsoft/tslocationmanager/2.14.1/tslocationmanager-2.14.1.aar.sha1

@@ -4,6 +4,6 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.transistorsoft</groupId>
   <artifactId>tslocationmanager</artifactId>
-  <version>2.14.1</version>
+  <version>2.14.4</version>
   <packaging>aar</packaging>
 </project>