BleManagerStopScan should be invoked on stopScan()
See original GitHub issueVersion
- react-native-ble-manager v6.5.0
- react-native v0.56.0
- Android v9
Expected behaviour
The BleManagerStopScan
event should be invoked when stopScan()
is called.
Actual behaviour
BleManagerStopScan
is only called when a scan finishes automatically (i.e. after seconds
have elapsed since calling scan()
) or when the scan fails.
Steps to reproduce
Call BleManager.stopScan()
. No event is triggered.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:14 (6 by maintainers)
Top Results From Across the Web
react-native-ble-manager - npm
stopScan(). Stop the scanning. Returns a Promise object. Examples. BleManager.stopScan().then(() => { // Success code console.log("Scan ...
Read more >react-native-ble-connect - npm package - Snyk
You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.
Read more >android - BluetoothAdapter won't stop scanning for BLE devices
If stopScan is called with new callback there is still some events delivered to previous callback before scan is stopped. If you will...
Read more >npm:@nois/react-native-ble-manager - Skypack.dev
stopScan(). Stop the scanning. Returns a Promise object. Examples BleManager.stopScan().then(() => { // Success code console.log("Scan ...
Read more >React Native BLE Communication Module - Morioh
In Android API 29 >= you need to use “ACCESS_FINE_LOCATION” instead of ... stopScan().then(() => { // Success code console.log("Scan stopped"); }); ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
was it fixed?
Yes, Is fixed only on iOS, my fault.