Results 3 comments of Sean Madden

I've been looking into this exact issue. My guess is that the windows recvfrom timeout call invalidates the socket upon timeout - it seems to be a quirk of winsock2....

Sending a packet before calling the iterator seems to bind the socket, preventing this error.

Still present in iOS 4.8.6.4. Is this on the roadmap somewhere to be addressed?