Open cjcdev opened 2 years ago
Can confirm this issue as well - we can see a connected event, but DeviceConnectionState.connecting never happens.
Any updates on this?
I am also having this issue. This comes as a big problem when the user decides to click on "Cancel" when the pair prompt appears. Because connecting never happens, the library thinks the user clicked on "Pair", which is not always true.
Anyway, when the prompt appears, library reports as connected, so there is actually no way to know for sure if the device is actually connected or not. Only way for me to do this right now is to attempt the connection 2 times.
Any better ideas?
This issue has actually been mentioned elsewhere: https://github.com/PhilipsHue/flutter_reactive_ble/issues/385#issuecomment-1040502145
And I can also confirm the linked comment - the "connecting" state isn't communicated on the first connect, but if I disconnect and reconnect, the "Connecting" state is seen.
Any news on the issue?
Did anyone find any better workaround for the 1st connection issue, or is disconnect and then reconnect the way to go for now?
Same issue here, any news regarding this?
This issue has actually been mentioned elsewhere: #385 (comment)
And I can also confirm the linked comment - the "connecting" state isn't communicated on the first connect, but if I disconnect and reconnect, the "Connecting" state is seen.
Warning! No event channel set up to report a connection update
is still happening on iOS in 5.0.2.Attempting but failing to mitigate the issue, I do several steps recommended in various issues
WidgetsFlutterBinding.ensureInitialized();
as the first line in mainFlutterReactiveBle ble
instance as soon as I have permission approvedble.initialize()
callThis sequence does not mitigate the issue but seems reliable for everything else.
I'm having the same issue on iOS using 5.0.3
Describe the bug On iOS, I do not receive DeviceConnectionState.connecting state before the Connected state.
On Android, I am always seeing Connecting state.
To Reproduce Steps to reproduce the behavior:
Expected behavior I should always see Connecting state prior to Connected state
Smartphone / tablet
Peripheral device