We're looking at around 2 weeks or so before we put out the official release.

Excellent news, thank you!

@benp thanks a lot, will check it out!

@caeduk Please post a new topic with specific steps to reproduce the issue you're having so we can investigate it on our end.

Undiscover will disconnect, but will not explicitly unbond.

Hello, we have similiar issue (also tested with setting autoBond to false/true has no affect). We noticed that the Sony Xperia 1 is connected to our BLE device and 60 seconds later it got unbound / unpaired from the smartphone. We tested it with different scenarios to exclude sources of issue (as it is a coffee machine we turned it off before the 60 seconds where over to verify that the coffee machine didnt caused this). My question is: can this be a issue by Sweetblue or is it more a Sony only issue ? (as it only happens on this devices).

@ryanbis I'm very glad 3.2.7 is released! Thank you for your prompt service. We are now verifying notify/write on single characteristic with setting UpdateThreadType as HANDLER_THREAD.

@ryanbis the fix to this connection loop went out with 3.2.3 right? I had implemented the methods in DefaultReconnectionFilter , to workaround the issue described here https://forum.sweetblue.io/topic/12/explicit-disconnect-triggers-automatic-reconnect/15 Now the workaround fails. How do we simply tell Sweetblue -- hey, disconnect now and do not retry to connect until we call connect() again?

Excellent, please let me know if you still see the problem.

@caeduk interesting, I didn't know that you can do that if you scan without filters. We can probably look into their source code and find more hints i.e. see under which conditions they trigger that notification to ask the user if they want to debug the connection

@hayashi Due to the way Azure Artifacts works, we were forced to create a new feed. See https://forum.sweetblue.io/topic/152/new-maven-server for the new URL (basically, just tack a 3 onto the second sweetblue in the url).

Well, it's mostly the connecting itself which is the issue... The scanning/finding is pretty consistent now...