FlutterBluePlus.state behaves strange.

[ghost]

There were similar issues in the upstream repository already:

• Stream get state does not return a broadcast stream
• FlutterBlue.state cancels all subscriptions if only one listener cancels

And it's still an issue. In my case a class that is provided with provider package at the root of the widget tree is trying to keep connection with any device that can act as a gateway to a mesh network between IoT devices. It's doing this in the background and listens to the state field to do it only when Bluetooth is turned on.

In the same time widgets that require gateway connection, so user can make any interaction with the network, are listening state to indicate that gateway is not available, because Bluetooth is turned off (other reasons may be that it's just not around or location services are disabled). Of course it's abstracted to a single class like BluetoothNotAvailableDialog, but this still leaves a single instance of that service class and multiple instances of the dialog class and they cannot listen to state field at the same time, because only one of them receives events and the rest do not.

There already exists a pull request which fixes the issue. It's pretty small change so should be easy to review and merge.

[SeekayOng]

Kindly solve this issue please

[MrCsabaToth]

Please merge that referenced PR pauldemarco/flutter_blue#609 so I don't have to maintain my own fork of a fork yet again.

[boskokg]

Thanks. commited

[MrCsabaToth]

Yes! My custom fork is now closer to the upstream!