Location request timed out most of the time.
See original GitHub issueIm using getCurrentPosition to get user location with following params.
enableHighAccuracy: false,
timeOut: 15000,
maximumAge: 10000,
Most of the time response will be Location request timed out. Only after getting the user location I can generate data based on that. Is there any way to fix this issue or should i try any other libraries.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:26 (5 by maintainers)
Top Results From Across the Web
React Native Android location request timed out - Stack Overflow
timeout (ms) - Is a positive value representing the maximum length of time (in milliseconds) the device is allowed to take in order...
Read more >Android - Location request timed out · Issue #90 - GitHub
It works on most of devices but in some cases its not even work on them and the error is always location request...
Read more >Solve “Location request timed out” problem when ... - Steve Mu
Solve “Location request timed out” problem when using geolocation in React Native. It took me a few hours just to make the navigator.geolocation...
Read more >intermittent network request timed out on iOS 13.4.1+
1. The most common reason this happens is because your app is inadvertently connecting to a server that you didn't expect to. To...
Read more >LocationRequest | Google Play services
Many location requests parameters are considered hints, ... small amount of time in case a high accuracy location can be delivered instead.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have this problem only with Android 10
If it’s android, some reported that opening google maps once will solve this issue. For iOS, I’m not sure what the issue could be. Are you using emulator or actual device?