[Bug]: autoConnect doesn't work about flutter_blue_plus HOT 10 CLOSED

I think I have figured out why it is not reconnecting automatically anymore.

There is a conceptual change how to react on BluetoothProfile.STATE_DISCONNECTED in the Gatt-callback: you destroy every time there is a "disconnection" all connection-data by calling gatt.close() although the connection was "only" lost for example because being out of range. In this case a later re-connection is not possible. The "old" version (until version 1.4.0) only called gatt.close() when the disconnection was initiated by the user but kept the connection-data in all other cases of disconnection.

@chipweinberger Can you confirm my analysis? Do you see any problem to change back to the previous concept of calling gatt.close() only when disconnect was initiated by the user?

from flutter_blue_plus.

thanks for your analysis

yes we changed the behavior of gatt.close to free up resources. Most phones only have enough resources for 6 connections, and will deny new connections. It is best to free resources automatically when the connection is lost.

that said, we could change the code to not call gatt.close if autoconnect is enabled for that connection.

in this case, the user will have to manually call disconnect to free up resources.

perhaps you can try that and let me know if it works.

That is a good idea and even an improvement to the "old" concept which kept the connection-data unnecessarily even without "autoConnect" activated.

I will create a PR.

from flutter_blue_plus.

should be fixed in 1.14.12

from flutter_blue_plus.

thanks for filing. I'm not sure the problem to be honest.

from flutter_blue_plus.

Same for me: in older versions of flutter_blue_plus (I can not say until which version) the auto-re-connect worked, too, and now it does work anymore.

from flutter_blue_plus.

I probably will not fix this issue myself.

if you figure it out, open a PR please.

from flutter_blue_plus.

thanks for your analysis

yes we changed the behavior of gatt.close to free up resources.
Most phones only have enough resources for 6 connections, and will deny new connections. It is best to free resources automatically when the connection is lost.

that said, we could change the code to not call gatt.close if autoconnect is enabled for that connection.

in this case, the user will have to manually call disconnect to free up resources.

perhaps you can try that and let me know if it works.

from flutter_blue_plus.

Well done @MartinXBcn. I'm sorry I can't help you guys on this. I don't have too much knowledge with native code.
Ets el rei Martin!

from flutter_blue_plus.

fixed in master: 9c44bc4

from flutter_blue_plus.

Thanks, @MartinXBcn @chipweinberger

from flutter_blue_plus.