I'm using API 2.1.3, and after several connections/disconnections with a peer device, I'm seeing the API never returning from a DiscoverPipes() call. It appears to be waiting for something but never timing out or throwing an exception, and in the Visual Studio console the following message is generated:
[] Waiting for HCI_Num_Completed_Packets_Event, nnnnnn second(s) elapsed
where n is a numerical digit. This causes the thread in my application to never return, which is something I'd like to avoid. I've tried two different Master Emulator devices (nRF2739 0.9.15536, and nRF51822 0.9.0.10022) with the same result. Why is this occurring, and how can it be mitigated? Is this a known issue, or has been fixed in a later release?
