BluetoothLE Extension ScanForService is not setting the Scanning flag to true

[Gerriko_io]

Hi all, it's been a good while since I last popped onto the community channel.

I just an anomaly with the BLE extension that I wanted to check.

I am using BLE Extension Version: 20200828 / Date Built: 2020-08-28

If I use the BluetoothLE. StartScanning method the BluetoothLE.Scanning flag will be correctly set to true.

However, I found that if I use the BluetoothLE. ScanForService method this flag is (incorrectly) not set to true.

Thanks.

[ABG]

I see a more recent version of the BLE extension at

FAQ Section: BlueTooth/BLE nb158 and later

BLE Releases BluetoothLE extension 20201223 released - ewpatton BluetoothLE extension 20200828 released - ewpatton BluetoothLE extension 20190701 released - EWPatton BLE Problems How to clean out residual BLE extension parts - ewpatton How to send text longer than 20 bytes - ChrisWard WriteStrings is fixed to 23 Bytes and WriteBytes uses MTU - F3John Multiple BLE connections in one screen - PeterO BLE app freezes then crashes - registered too many times - Patton BLE Techniques FAQ Sec…

[ewpatton]

Actually the bug is more subtle than that. I reviewed the code and it looks like isScanning is set to true on the first scan result. So the only reason it "works" in StartScanning is because it finds a device before you check a flag whereas in the ScanForService method it doesn't. If you put your phone inside of a faraday cage and tried again you'd get the same result where isScanning is false. I'll need to think about how we can improve the logic there.

[Gerriko_io]

@ABG thanks for the link to the updated version. Problem still exists.

@ewpatton thanks for the response. Aha, so it's also deviceList related. In that case I can try and do my own workaround by checking to see if deviceList is empty or if not and scanning is true etc.