@rn-bridge/react-native-geofencing

React native module to determine if a location is within defined geographical boundaries. Geofencing combines awareness of the user's current location with awareness of the user's proximity to locations that may be of interest. To mark a location of interest, you specify its latitude and longitude. To adjust the proximity for the location, you add a radius. The latitude, longitude, and radius define a geofence, creating a circular area, or fence, around the location of interest.

Fully compatible with TypeScript & Turbomodules.

Required React Native Version >=0.72.0

Supported platforms

Installation

npm install @rn-bridge/react-native-geofencing

or

yarn add @rn-bridge/react-native-geofencing

Configuration and Permissions

iOS

To enable geofence in your app, you need to add the NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription keys to your Info.plist file. If your app supports iOS 10 or earlier, you must also include the NSLocationAlwaysUsageDescription key. Without these keys, geofence requests will fail.

To enable geofence while the app runs in the background, add the NSLocationAlwaysUsageDescription key to Info.plist.

It’s important to ensure you’ve enabled the necessary background modes. Here’s how to do so:

• Go to your Xcode project settings.
• Select your target.
• Go to the Signing & Capabilities tab.
• Enable Background Modes capability.
• Check Location updates

Your Info.plist should look like this, Explain why the background location is required!!

<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>This app need your location to provide best feature based on location</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>This app need your location to provide best feature based on location</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>This app need your location to provide best feature based on location in background</string>
<key>UIBackgroundModes</key>
<array>
  <string>location</string>
</array>

Android

The first step in requesting geofence monitoring is to request the necessary permissions. To use geofencing, your app must request the following:

• ACCESS_FINE_LOCATION
• ACCESS_BACKGROUND_LOCATION if your app targets Android 10 (API level 29) or higher

Your AndroidManifest.xml should look liks this

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android">

  <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
  <uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION" />
  <uses-permission android:name="android.permission.WAKE_LOCK" />

</manifest>

Summary

Methods

• requestLocation
• getLocationAuthorizationStatus
• getCurrentLocation
• addGeofence
• removeGeofence
• getRegisteredGeofences

Listeners

• onEnter
• onExit
• removeOnEnterListener
• removeOnExitListener
• isOnEnterListenerAdded
• isOnExitListenerAdded

Usage

requestLocation

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.requestLocation({ allowWhileUsing: true });

Response:

{
  "success": true,
  "location": "WhenInUse"
}

To request background location:

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.requestLocation({ allowAlways: true });

Response:

{
  "success": true,
  "location": "Always"
}

Supported options:

• allowWhileUsing (Boolean) - App can use all location services and receive events while the app is in use.
• allowAlways (Boolean) - App can use all location services and receive events even if the user is not aware that your app is running. If your app isn’t running, the system launches your app and delivers the event.

[!WARNING] Android needs background location for geofencing to work. You must request location Allow all the time from the user. While iOS works with both while using and always

getLocationAuthorizationStatus

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.getLocationAuthorizationStatus();

Response: WhileInUse Always Denied

getCurrentLocation

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.getCurrentLocation();

Reponse:

{
  "altitude": 0,
  "city": "Coimbatore",
  "country": "India",
  "isoCountryCode": "IN",
  "latitude": 10.9314,
  "longitude": 76.9781,
  "name": "Eachanari", 
  "postalCode": "641021",
  "state": "TN",
  "timeZone": "Asia/Kolkata"
}

addGeofence

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.addGeofence({
        id: 'a9957259-8036-4dcb-974c-34eae9b44bdb',
        latitude: 16.153062,
        longitude: 100.281585,
        radius: 500
    })

Response:

{
  "success": true,
  "id": "a9957259-8036-4dcb-974c-34eae9b44bdb"
}

Supported options:

• id (String) - Set the ID of the geofence. This is a string to identify this geofence.
• latitude (Double) - The latitude and longitude are used to define the precise geographical location of the geofence’s center. This ensures accurate detection when a device enters or exits the geofenced area.
• longitude (Double) - The latitude and longitude are used to define the precise geographical location of the geofence’s center. This ensures accurate detection when a device enters or exits the geofenced area.
• radius (Integer) - The radius defines the boundary of the geofence around the central point (latitude and longitude). It allows for flexibility in creating different-sized geofences

Choose the optimal radius for your geofence

For best results, the minimum radius of the geofence should be set between 100 - 150 meters. When Wi-Fi is available location accuracy is usually between 20 - 50 meters. When indoor location is available, the accuracy range can be as small as 5 meters. Unless you know indoor location is available inside the geofence, assume that Wi-Fi location accuracy is about 50 meters.

When Wi-Fi location isn't available (for example, when you are driving in rural areas) the location accuracy degrades. The accuracy range can be as large as several hundred meters to several kilometers. In cases like this, you should create geofences using a larger radius.

removeGeofence

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.removeGeofence(id)

Response:

{
  "success": true,
  "id": "a9957259-8036-4dcb-974c-34eae9b44bdb"
}

Supported options:

• id (String) - The ID uniquely identifies a geofence, enabling precise and efficient removal by referencing the specific geofence without ambiguity.

getRegisteredGeofences

import Geofencing from '@rn-bridge/react-native-geofencing';

const response = await Geofencing.getRegisteredGeofences()

Response:

["id1", "id2", "..."]

Constants

import { Events } from '@rn-bridge/react-native-geofencing';

import { Authorization } from '@rn-bridge/react-native-geofencing';

[!IMPORTANT]

Listening for location transitions

onEnter

import Geofencing, { Events } from '@rn-bridge/react-native-geofencing';

Geofencing.onEnter((ids: string[]) => {
  console.log(Events.Enter, ids);
});

Response:

["id1", "id2", "..."]

onExit

import Geofencing, { Events } from '@rn-bridge/react-native-geofencing';

Geofencing.onExit((ids: string[]) => {
  console.log(Events.Exit, ids);
});

Response:

["id1", "id2", "..."]

removeOnEnterListener

import Geofencing from '@rn-bridge/react-native-geofencing';

Geofencing.removeOnEnterListener()

removeOnExitListener

import Geofencing from '@rn-bridge/react-native-geofencing';

Geofencing.removeOnExitListener()

isOnEnterListenerAdded

import Geofencing from '@rn-bridge/react-native-geofencing';

Geofencing.isOnEnterListenerAdded() // true or false

isOnExitListenerAdded

import Geofencing from '@rn-bridge/react-native-geofencing';

Geofencing.isOnExitListenerAdded() // true or false

Troubleshoot the geofence entrance event (Android)

Here are some possible reasons for alerts not working as expected:

• Accurate location isn't available inside your geofence or your geofence is too small. On most devices, the geofence service uses only network location for geofence triggering. The service uses this approach because network location consumes much less power, it takes less time to get discrete locations, and most importantly it’s available indoors.
• There is no reliable network connectivity inside your geofence. If there is no reliable data connection, alerts might not be generated. This is because the geofence service depends on the network location provider which in turn requires a data connection.
• Alerts can be late. The geofence service doesn't continuously query for location, so expect some latency when receiving alerts. Usually the latency is less than 2 minutes, even less when the device has been moving. If Background Location Limits are in effect, the latency is about 2-3 minutes on average. If the device has been stationary for a significant period of time, the latency may increase (up to 6 minutes).

How To Run Example App ?

To run example app, follow the below steps

1. Clone the repository
2. Do yarn install
3. For androidyarn example android
4. For iOS cd ios and do bundle exec pod install and run the iOS app from XCode

Demo Video

Android
iOS