transistorsoft / flutter_background_geolocation

Sophisticated, battery-conscious background-geolocation & geofencing with motion-detection
https://www.transistorsoft.com/shop/products/flutter-background-geolocation
Other
650 stars 241 forks source link

Geofencing not working accurately #1360

Open pratikbutani opened 1 month ago

pratikbutani commented 1 month ago

I've implemented geofencing in my app where I want to check whether user is entered/exited from given radius. Its working fine but taking time to give status and if radius is less than 50 meters, it's not giving an update even if I walk 70-80 meters.

Here is the video: I've printed log on ENTER/EXIT but it is not occurring on EXIT as well as on ENTER (Second time)

  1. EXITing but onGeofenceChange is not getting called: Radius is 35 meters

https://github.com/user-attachments/assets/4ba63777-7fe3-4fad-aff6-b68e58152a3b

  1. ENTERING AGAIN but onGeofenceChange is not getting called: Radius is 35 meters

https://github.com/user-attachments/assets/b0e0cb51-1ba5-4b42-9000-62299730acc0

Your Environment

Expected Behavior

If should give the update on change of Geofence status whether it is ENTERed or EXITed.

Actual Behavior

It is only giving an update if we go more ahead then border line of Geofence.

Steps to Reproduce

  1. Add Geofences with radius less than 100.
  2. Checking by Walking

Context

I want to cover my office area through geofence so I can check whether any user is entered/exited into/from the office.

christocracy commented 1 month ago

Add Geofences with radius less than 100.

The minimum geofence radius is 150 meters.

When having issues, set debug: true so you can hear debug sound FX.

pratikbutani commented 1 month ago

Hello @christocracy, I'd tried with 200 meters radius as well.

The event only occurs if I move further ahead of the geofence line.

Do I need to change anything in the configuration or it will work as it is.

christocracy commented 1 month ago

Do I need to change anything in the configuration

no.

The event only occurs if I move further ahead of the geofence line.

geofences are not guaranteed to fire exactly at the radius. It is perfectly normal that they can fire late.

if it works, it works.

github-actions[bot] commented 10 hours ago

This issue is stale because it has been open for 30 days with no activity.