To help you get started, we've collected the most common ways that react-native-ble-plx is being used within popular public projects.

LedgerHQ / ledgerjs / packages / react-native-hw-transport-ble / src / index.js View on Github

static listen(observer: *) {
    let bleManager;
    try {
      bleManager = new BleManager();
    } catch (e) {
      // basically for the tests to pass
      console.warn(e);
      return { unsubscribe: () => {} };
    }
    const unsubscribe = () => {
      sub.remove();
      bleManager.stopDeviceScan();
    };
    const onBleStateChange = (state: string) => {
      if (state === "PoweredOn") {
        bleManager.startDeviceScan(null, null, (bleError, device) => {
          if (bleError) {
            observer.error(bleError);
            unsubscribe();
            return;

View more ways to use react-native-ble-plx

About this library

It supports:

• observing device's Bluetooth adapter state
• scanning BLE devices
• making connections to peripherals
• discovering services/characteristics
• reading/writing characteristics
• observing characteristic notifications/indications
• reading RSSI
• negotiating MTU
• background mode on iOS
• turning the device's Bluetooth adapter on

It does NOT support:

• bluetooth classic devices.
• communicating between phones using BLE (Peripheral support)
• bonding peripherals
• beacons

Table of Contents

1. Compatibility
2. Recent Changes
3. Documentation & Support
4. Configuration & Installation
5. Troubleshooting
6. Contributions

Compatibility

For old RN versions (<0.60) please check old README (1.x) for the old instructions or migration guide.

Recent Changes

3.2.0

• Added Android Instance checking before calling its method, an error will be visible on the RN side
• Added information related to Android 14 to the documentation.
• Changed destroyClient, cancelTransaction, setLogLevel, startDeviceScan, stopDeviceScan calls to promises to allow error reporting if it occurs.
• Fixed one of the functions calls that clean up the BLE instance after it is destroyed.

Current version changes All previous changes

Documentation & Support

Interested in React Native project involving Bluetooth Low Energy? We can help you!

Documentation can be found here.

Quick introduction can be found here

Contact us at intent.

Configuration & Installation

Expo SDK 43+

> Tested against Expo SDK 49 > This package cannot be used in the "Expo Go" app because it requires custom native code. > First install the package with yarn, npm, or npx expo install.

After installing this npm package, add the config plugin to the plugins array of your app.json or app.config.js:

{
  "expo": {
    "plugins": ["react-native-ble-plx"]
  }
}

Then you should build the version using native modules (e.g. with npx expo prebuild command). And install it directly into your device with npx expo run:android.

You can find more details in the "Adding custom native code" guide.

API

The plugin provides props for extra customization. Every time you change the props or plugins, you'll need to rebuild (and prebuild) the native app. If no extra properties are added, defaults will be used.

• isBackgroundEnabled (boolean): Enable background BLE support on Android. Adds `` to the AndroidManifest.xml. Default false.
• neverForLocation (boolean): Set to true only if you can strongly assert that your app never derives physical location from Bluetooth scan results. The location permission will be still required on older Android devices. Note, that some BLE beacons are filtered from the scan results. Android SDK 31+. Default false. WARNING: This parameter is experimental and BLE might not work. Make sure to test before releasing to production.
• modes (string[]): Adds iOS UIBackgroundModes to the Info.plist. Options are: peripheral, and central. Defaults to undefined.
• bluetoothAlwaysPermission (string | false): Sets the iOS NSBluetoothAlwaysUsageDescription permission message to the Info.plist. Setting false will skip adding the permission. Defaults to Allow $(PRODUCT_NAME) to connect to bluetooth devices.

> Expo SDK 48 supports iOS 13+ which means NSBluetoothPeripheralUsageDescription is fully deprecated. It is no longer setup in @config-plugins/react-native-ble-plx@5.0.0 and greater.

Example

{
  "expo": {
    "plugins": [
      [
        "react-native-ble-plx",
        {
          "isBackgroundEnabled": true,
          "modes": ["peripheral", "central"],
          "bluetoothAlwaysPermission": "Allow $(PRODUCT_NAME) to connect to bluetooth devices"
        }
      ]
    ]
  }
}

Legacy Expo (SDK < 43)

1. Make sure your Expo project is ejected (formerly: detached). You can read how to do it here. (only for Expo SDK < 43)
2. Follow steps for iOS/Android.

iOS (example setup)

1. npm install --save react-native-ble-plx
2. Enter ios folder and run pod update
3. Add NSBluetoothAlwaysUsageDescription in info.plist file. (it is a requirement since iOS 13)
4. If you want to support background mode:
   • In your application target go to Capabilities tab and enable Uses Bluetooth LE Accessories in Background Modes section.
   • Pass restoreStateIdentifier and restoreStateFunction to BleManager constructor.

Android (example setup)

1. npm install --save react-native-ble-plx

2. In top level build.gradle make sure that min SDK version is at least 23:

   buildscript {
       ext {
           ...
           minSdkVersion = 23
           ...
   

3. In build.gradle make sure to add jitpack repository to known repositories:

   allprojects {
       repositories {
         ...
         maven { url 'https://www.jitpack.io' }
       }
   }
   

4. In AndroidManifest.xml, add Bluetooth permissions and update ``:

   
   
      ...
   
      
      
      
      
      
      
      
      
   
      
      
   
       ...
   

5. (Optional) In SDK 31+ You can remove ACCESS_FINE_LOCATION (or mark it as android:maxSdkVersion="30" ) from AndroidManifest.xml and add neverForLocation flag into BLUETOOTH_SCAN permissions which says that you will not use location based on scanning eg:

    
    
    
    
    
    
    
    
   
       ...
   

   With neverForLocation flag active, you no longer need to ask for ACCESS_FINE_LOCATION in your app

Troubleshooting

Contributions

• Special thanks to @EvanBacon for supporting the expo config plugin.