Iftekhar Rifat
Iftekhar Rifat
Hello, can you describe the reason to expose this API ? Also when to call it from a user's perspective ?
Thanks for providing detailed steps, I'll see if I can reproduce this on my end and provide a fix if possible. As a workaround, you can use `watchPosition` and get...
`v5.3.0-beta.4` released, check if it solves your issue.
Update your play services location version to 18.0.0 or above. It should fix the issue. [https://developers.google.com/android/guides/releases#february_18_2021](https://developers.google.com/android/guides/releases#february_18_2021)
Thanks for the PR! Just a few observations 1. You don't need custom `putIntoMap` function. `Arguments` class provides a super helpful `fromBundle` method which you can use to convert `Bundle`...
Not related to the package, we don't have custom logic for different type of devices. Maybe iPhone 6 can't get a proper location fix and reporting inaccurate results. Best option...
Nice finding :), but users need to have at least 17.1.0 google play service version for this to work. Should we force users to update to the newer versions ?...
I'll try implementing this. I'm currently rewriting the android implementation to add support for android's default location manager api if google play service is not available. You can check [here](https://github.com/Agontuk/react-native-geolocation-service/tree/android-rewrite),...
This library does not track the state of the application. You should use Headless JS for doing background work and call geolocation API there.
Not sure, I'll take a look.