In what thread is your asynchronous TCP event processing occurring?
All scan results are processed by the network worker thread and if that thread is blocked your scan handler will not be called.
I am not precisely sure of the thread, but I use wiced_tcp_register_callbacks as shown in the tcp_server_async snip, so I would assume it does use the network worker thread.
Is there a follow up question or more information needed?
No more questions, my TCP events were running on the network worker thread, so I had to change the thread of the TCP events. Scanning works well now.