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.

@alejandrohcruz Set autoBondFixes to false.

@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

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

Yes, those trigger. We added those when we noticed that the times we set in taskTimeoutRequestFilter or DefaultTaskTimeoutRequestFilter weren't triggering.

Gotcha, sounds great!