Albert Sun 24b9889fb2 Location (iOS): Call back on requests only if they pass age and accuracy filters ...

Summary:
iOS pretty much always immediately updates location with the last cached location. This leads to the getCurrentPosition() API often returning this stale location. This change adds filtering to keep waiting until CLLocationManager provides a location fix that passes the requirements for each pending request.

This is potentially breaking in that clients that rely upon getCurrentPosition being extremely fast may find that location fixes take longer than before. However in such cases they should relax their requirements for maximumAge and/or accuracy.

Reviewed By: mmmulani

Differential Revision: D13889626

fbshipit-source-id: f566314ed5968151dad0839b99e0d3c9a562af13

2019-02-25 14:21:36 -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 (iOS): Call back on requests only if they pass age and accuracy filters

2019-02-25 14:21:36 -08:00

React-RCTGeolocation.podspec

Split React.podspec into separate podspecs for each Xcode project (#23559)

2019-02-21 18:35:44 -08:00