Oli Barnett bbcb97a29a Location Services: don't reset desiredAccuracy on every update/error (#23209) ... Summary: See https://github.com/facebook/react-native/issues/7680. On iOS the RCTLocationObserver delegate is overriding `desiredAccuracy` every time CLLocationManager calls `didUpdateLocations` or `didFailWithError`. `desiredAccuracy` is reset to `RCT_DEFAULT_LOCATION_ACCURACY` (100 meters) This effectively makes it impossible for a react-native app to use any location accuracy other than the default. This commit simply removes the code which resets the desired accuracy, as there seems to be no rationale for doing so. The reset code was added as part of [a large general change](705a8e0144) so the original intention is unclear from the history. If somebody can explain it to me, I'm happy to rework this PR accordingly. Changelog: ---------- [iOS] [Fixed] - Location Services accuracy constantly reset to default of 100 meters. Pull Request resolved: https://github.com/facebook/react-native/pull/23209 Differential Revision: D13879497 Pulled By: cpojer fbshipit-source-id: f3c6c9c5ef698b23b99c407fd764ac990d69bf8c		2019-01-30 10:23:58 -08:00
..
RCTGeolocation.xcodeproj	Update Xcode projects (#19574)	2018-06-19 23:48:12 -07:00
Geolocation.js	Use `invariant` instead of `fbjs/lib/invariant`	2018-12-03 00:07:02 -08:00
RCTLocationObserver.h	Update copyright headers to yearless format	2018-09-11 15:33:07 -07:00
RCTLocationObserver.m	Location Services: don't reset desiredAccuracy on every update/error (#23209)	2019-01-30 10:23:58 -08:00