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.
watchPosition doesn't raise an error if the user disables location services
See original GitHub issueWhen a user opens the app with location services enabled, and the app then registers a watchPosition callback, and then the user disables location services, and goes back to the app, watchPosition never raises an exception. React Native core’s navigator.geolocation has this same issue, but I would expect watchPosition to raise an exception the same way that getCurrentPosition would. This would be useful for detecting that location services are off so the app could prompt a user to reenable it.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Same issue. And in addition: If I run my application with disabled GPS, then i click “No thanks” on request to turn GPS on (after that errorCallback is triggering), and then I manually turn GPS on - nothing happens after that (I expect that successCallback should be triggered).
It should be fixed in v5.0.0. Sorry for not being able to fix this sooner.