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.

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

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

Hi, I'm jumping back into this thread with more information and a couple of questions: The Nordic's nRF Connect app can detect when I connect the BLE peripheral on my own app and directly interact with it. Which is pretty cool. Also, when you open up their application and you click 'connect' on a bonded device that is already connected (using my own app), their app connects the services and is able to interact with the peripheral device. Q1: How could I achieve the behavior described by point #2? Either manually (user interaction required) or automatically? i.e. when I open up my app, it should detect bonded devices that are connected and enable them to be used right away by the user.

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

Gotcha, sounds great!

Glad to hear! Looking forward to the next release.

We are using sweetblue v2 with xamarin. I needed to basically create a java wrapper interface around the bledevice methods which required callbacks/listeners. The bindings compilation had issues with the generic type java features being used with the listeners, so I just call to my java wrapper object from c# which has simple listeners and the binding generation has no issues with. I've attached our wrapper's source code for you to use, it filters the scans without needing to call back into c# too which was a huge performance improvement.sweetbluewrapper