Moo 1874/fused location patch - 10.18 #78
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
after replacing react-native-geolocation-service, we started getting the timeout error.
I found out that
Community package uses LocationManager.requestLocationUpdates(...) flow via your native modules while geolocation-service using Fused Location Provider.
Fused location provider works faster for following reasons
1- Fuses GPS, Wi-Fi, cell-tower, and sensors to get a “good enough” fix almost instantly.
2- Returns the last known location immediately and only then tries to get a fresh reading.
3- Lets you configure a single high-accuracy request (and tear it down) instead of spinning up a continuous listener.
I applied a patch within community package to use same provider.