Are there any chances that getCurrentPositionAsync() can return cached location?

syamk · December 29, 2021, 10:59am

Requests for one-time delivery of the user’s current location. Depending on given accuracy option it may take some time to resolve, especially when you’re inside a building.

As per above info from expo documentation, getCurrentPositionAsync() returns the current location of the user. But I have observed in my React-Native app that getCurrentPositionAsync() returns some other locations when I try to get current location.

Hence, I would like to know that, Are there any chances that getCurrentPositionAsync() can return cached location?

Topic		Replies	Views
getCurrentPositionAsync() returns location which is far from actual location Expo Development Tools location	0	241	January 18, 2022
getCurrentPositionAsync doesn't return location Expo SDK	1	571	November 27, 2018
getCurrentPositionAsync() doesn't always return on Android Expo SDK location	1	292	January 11, 2023
getCurrentPositionAsync() is taking too much time to fetch location in iOS devices Expo Development Tools location	6	508	September 23, 2022
Location.getCurrentPositionAsync is very slow on Android (only)? Expo SDK	3	1289	September 20, 2019

Are there any chances that getCurrentPositionAsync() can return cached location?

Related Topics