-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't find peripherals that implement extended advertising #571
Comments
Further to the information provided above, we have tried using sample firmware provided with the nRF52840-DK and configured it to use Bluetooth 5 Advertising Extension. The peripheral shows up on nRF Connect on the Google Pixel 6 but not in my custom Flutter App. Is this not supported by flutter_reactive_ble? |
Im having the same problem. It seems RxAndroidBle does not support extended advertising yet (dariuszseweryn/RxAndroidBle#774 ) |
Soon RxAndroidBle will support extended advertising! Check the PR: Here is the change flutter_reactive_ble will need: |
@Taym95 is there any ETA for a release with the fix? |
@danielstuart14, I will make new release |
Any news about that? |
Would be great if this issue can be opened again, until a new release is out. Edit: Until there is a new release, people who need this update can use the master branch of this repository by entering the following in your pubspec.yaml dependency_overrides: |
Describe the bug
Since our peripheral switched to using extended advertising, I have not been able to find the peripheral when performing a scan. It was previously working when the peripheral used standard advertising.
To Reproduce
Steps to reproduce the behavior:
_ble.scanForDevices(withServices: withServices)
Expected behavior
To find the peripheral
Smartphone / tablet
Peripheral device
Additional context
This is an android specific bug as both advertising models work on iOS. Also, peripherals using extended advertising do appear in the scan results of the nRF Connect App on the Android Pixel 6.
The text was updated successfully, but these errors were encountered: