[Help Wanted]: "Enter" event is triggered a lot of times inside one geofence

[Crysp]

Required Reading

• Confirmed

Plugin Version

4.19.0

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

Xiaomi

Device operating-systems(s)

Android 13

React Native / Expo version

0.82.1

What do you require assistance about?

Generally geofence events triggers as usual (as described in doc), but in this case there are a lot of "enter" events while user stay inside geofence. I thought it could be because of location jumping, but there are no "exit" event, and location seems isn't jumping. Could you help to understand the reason of this issue?

Large logs in the gist

https://gist.github.com/Crysp/2e8a71922e4dace84916ad0b0fb8df46

[Optional] Plugin Code and/or Config

[Optional] Relevant log output

[christocracy]

Android geofences are re-registered and their entry-state reset if:

• Device location services disabled
• Device rebooted
• Location Always permission revoked.
• App Reinstallation or Data Clearing: If the app is uninstalled and reinstalled, or its data is cleared
• Google Play Services Data Cleared
• GEOFENCE_NOT_AVAILABLE Alert: If your app receives a GEOFENCE_NOT_AVAILABLE status code (e.g., if the Network Location Provider is disabled), you may need to re-register geofences after the issue is resolved.

The OS is completely responsible for managing when geofence events are fired. The OS is like an Amazon delivery driver, delivering geofences to this SDK's door. The SDK has no option but to accept the delivery when it arrives.

[Crysp]

Looks like no one of these reasons affects user. Events triggers every day when user arrives at geofence. start() / stop() (monitoring location) could not be the reason?

[christocracy]

Yes, when you call .stop(), geofence entry-states are cleared.

Calling .start() after .stop() will cause a geofence to fire again.