You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that the Windows implementation of this plugin currently lacks support for BLE extended advertising. As a result, devices using extended advertising features, such as coded PHY, aren’t detected during scans.
This can be addressed by enabling BluetoothLEAdvertisementWatcher.AllowExtendedAdvertisements after the watcher is instantiated. I’d be happy to submit a pull request to make this change if you’re open to supporting this feature.
Hey, because there are multiple platforms involved, it would be great if we have some info about rest of the platforms as well, and then decide the Api behaviour
Sorry for the delay in responding. I have tested the package on the Android platform. I can confirm devices using extended advertising features are discovered when scanning, no changes are required.
I unfortunately cannot test for Mac or iOS as I do not have Apple devices available.
I would suggest this setting be enabled by default on Windows without necessarily adding an API option. Legacy advertising devices could still be seen during scanning, and this would bring the Windows version in line with the Android version.
Hello,
I've noticed that the Windows implementation of this plugin currently lacks support for BLE extended advertising. As a result, devices using extended advertising features, such as coded PHY, aren’t detected during scans.
This can be addressed by enabling BluetoothLEAdvertisementWatcher.AllowExtendedAdvertisements after the watcher is instantiated. I’d be happy to submit a pull request to make this change if you’re open to supporting this feature.
More details here
The text was updated successfully, but these errors were encountered: