If app is in background mode then entry and exit not working

[sarishti]

If app is in background mode/ kill state then entry and exit not working in case of android

[michaelmika]

Do you mean the "Monitoring Geofence" or a "normal" Geofence? This library uses the native Geofencing abilities of the OS (See: Android or iOS. It's limited to the native's abilities (e.g. number of geofences, OS version, etc.). It is not the most accurate geofencing, but batterie saving and efficient, that's why it can sometimes take a bit to get the notification. Which OS are you using?

In case you mean the "Monitoring Geofence" check the Topic in the Docs (at the end) for it's implementation depending the OS.

[sarishti]

I am using normal geofence and I am using OS version 9 on s8 device. In case of ios It is working fine during background mode and push me notification but in android it is not working.

[michaelmika]

Have you enabled your device to let Apps use high (fine) accuracy location? See here.
This module does not ask if the permission is granted (because I had trouble in another Project with it). You might want to ask the user at the beginning of your App. It is pretty simple in React:

async function requestLocationPermission() {
  try {
    const granted = await PermissionsAndroid.request(
      PermissionsAndroid.PERMISSIONS.ACCESS_FINE_LOCATION,
      {
        title: 'Location Permission for geofencing',
        message:
          'We need that permission for the geofencing feature',
        buttonNeutral: 'Ask Me Later',
        buttonNegative: 'Cancel',
        buttonPositive: 'OK',
      },
    );
    if (granted === PermissionsAndroid.RESULTS.GRANTED) {
      console.log('You can use the Location now');
    } else {
      console.log('Location permission denied');
    }
  } catch (err) {
    console.warn(err);
  }
}

see react docs

[ghost]

I think after Oreo (Android 8) they don't let you do location stuff Inna back ground service and you have to start a foreground service with a notification. I might be wrong but it looks similar to this issue in another module which has a fork to fix it.

eddieowens/react-native-boundary#45