[Bug]: getCurrentPosition reuses inaccurate location

[mlev]

Required Reading

• Confirmed

Plugin Version

5.0.5

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

Google Pixel 7

Device operating-systems(s)

Android 16

React Native / Expo version

0.81.5, Expo 54

What happened?

When I call getCurrentPosition the documentation says it will always use maximum accuracy regardless of the requested configuration. But for me it is reusing an old location with >100m accuracy. I can see in the logs a message from trySatisfyLastLocation that the desiredAccuracy is -1 but also that meetsAccuracy: true, which seems wrong.

For the main tracking session I am using a Medium accuracy - but the documentation for getCurrentPosition implies this will be disregarded, which is why I am calling it when I need a high accuracy location.

Plugin Code and/or Config

{}

Relevant log output

04-06 10:55:58.940 INFO [TSLog log] 
  ℹ️  Triggering high accuracy request: Location accuracy: 142.5, Last accurate: 2026-04-06T00:45:34.693Z)
04-06 10:55:58.944 DEBUG [SingleLocationRequest trySatisfyLastLocation] 📍  
╟─ age: 1821ms
╟─ maximumAge: 0
╟─ desiredAccuracy: -1.0
╟─ meetsAccuracy: true
╟─ meetsStaleness: true

04-06 10:55:58.946 INFO [TSLocationManager a] 
╔═════════════════════════════════════════════
║ getCurrentPosition LocationResult: 35 (1822ms old)
╠═════════════════════════════════════════════
╟─ 📍  Location[fused -33.777218,151.293411 hAcc=142.5 et=+14d3h29m49s611ms alt=49.89317257291648 vAcc=6.9813647 {Bundle[{persist=true}]}], time: 1775436957123