React Native Bluetooth Classic was developed to bridge the gaps in the available React Native Bluetooth moduless:
are both fantastic implementations but they fall back to BLE on IOS.
The hardware in which my company was working would only communicate over Bluetooth Classic and required communication through the External Accessory framework. Please note that while working with this library on IOS, you'll need to become accustomed with the Apple and their MFi program. Here are some links to check out:
The Android functionality is pretty common and well documented, there are a number of examples which can be reviewed:
The project doesn't follow semantic versioning. It started with just some random versioning in order for me to determine the actual best way to do this. The final product moving forward is going to be:
so for example:
1.60.5 would be:
- React Native Bluetooth Classic v1 (breaking changes will increase)
- React Native v60.x - which will remain the current version until React Native provides breaking changes. When this occurs the next version would be
- 5 releases within the previous grouping
|0.9.x||0.59.9||4.1 (16)||IOS 9||releases/0.9.x|
|0.10.x||0.60.0||4.1 (16)||IOS 9||releases/0.10.x|
|1.60.x||0.60.0||8.0 (24)||IOS 9||master|
It may be possible to use the library in lower versions that those noted, if you confirm it working, please submit a pull request with updated version details.
Please see the change log for complete(ish) details.
Installation, like almost everything, is done through
$ npm install react-native-bluetooth-classic --save
Once installed autolinking will take over within your application.
With the changes in v1.0.0 it's possible that Autolinking doesn't actually work (just be prepared for that). The goal is to have it 100% working and customizable as per the React Native documentation, but until then just beware.
- stack trace
Feel free to submit any pull requests. Try to document which issue (if any) it resolves, or provide some details on what you're adding. I regularly try to look at the forks to see what changes there are and if there is value in adding them to the project.
Please update it accordingly when submitting a pull request!!