react-native-geolocation-service
react-native-geolocation-service copied to clipboard
Agontuk
Getting wrong position but accuracy saying it's in the radius
On a real device, sometimes i'm receiving wrong position with accuracy property saying approx. 20 - 100 meters but actually it's 1.3 kilometers away from my previous location causing inaccuracy on my tracking application.
Platfrom: Android React Native: 0.61.5
I am actually facing the same issue; but sometimes with error of up to 100kilometers.
This seems to happen totally randomly on some android devices (haven't been able to reproduce it myself, but my app has millions of users and it does happen a lot)
For example, users from singapore are ALWAYS found in Indonesia...
Did you find any kind of fix @replecta ?
@pierroo Unfortunately i haven't. I'm still stuck with it.
Have you tried the basic @react-community/react-native-geolocation?
I am starting to believe that on some android device this "FusedLocationProviderClient API" brought by this plugin is actually not working...
I don't think there's much I can do regarding this. Location will always be inexact since it's depending on many factors, so this kind of issue will popup sometimes. At best, you can filter the location you're getting by comparing the accuracy with previous one.
But if you find a solution for this, please let me know :)
In our case we always get accuracy >2000m. Is it possible that useHighAccuracy=true falls back to low accuracy if the GPS is off?
Same issue @react-community/react-native-geolocation very good accuracy but alot of errors react-native-geolocation-services no errors but very less accuracy
Chances are you're getting a coarse location and not a GPS location. It's hard to tell with Fused provider - maybe the speed is always 0? That's a good sign it's a coarse location. Why this is the case, I do not know. Maybe the GPS is off or the permission for high accuracy is not granted, so it's resulting in only wifi/cell tower/coarse location updates.
