Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

getCurrentPosition slow if Precise Location is set to Off on iOS 14

See original GitHub issue

If Precise Location is set to Off in settings, getCurrentPosition() takes from my testing ~10 seconds to resolve the location.

Happens irregardless of what enableHighAccuracy is set to.

Tested on both simulator and physical device with the same results. Using the master branch.

Issue Analytics

State:
Created 3 years ago
Reactions:10
Comments:7 (2 by maintainers)

Top GitHub Comments

3reactions

Agontukcommented, Feb 1, 2021

v5.2.0 has been published with location delay fix.

3reactions

NoahFacecommented, Dec 16, 2020

The cause of this issue is the following in RNFusedLocation.swift:

let locManager = CLLocationManager()
locManager.delegate = self
locManager.desiredAccuracy = getAccuracy(options)
locManager.distanceFilter = distanceFilter
locManager.startUpdatingLocation() //<<<<<<<<<<<<< requestLocation()

If you change requestLocation() to startUpdatingLocation(), IOS location services will start returning location values immediately rather than after 10 seconds. I don’t know the code well enough to tell you if this will impact subscriptions, but if you just want one-off location reads this will fix the issue.