Possible uncaught exception triggered by socket_write_close shutdown

Sorry I haven't filled in this bug report correctly. I've searched around for the bug tracker for 30 minutes and can't find anyone else reporting this issue.

This problem is fairly easy to replicate.

When downloading a file in iOS 10 if the app is put to sleep during the file download process. When the app is woken up again an exception appears to be thrown but nothing is reported to the error callback.

If the same error occurs ( Socket is not connected ) while the app is awake it does trigger the error callback correctly.

I've included the error message shown in the log below:

2016-12-05 12:22:17.279091 GuidedMind[8705:5171369] [] nw_socket_write_close shutdown(12, SHUT_WR): [57] Socket is not connected
2016-12-05 12:22:17.279144 GuidedMind[8705:5171369] [] nw_endpoint_flow_service_writes [15.1 52.216.16.91:443 ready socket-flow (satisfied)] Write request has 0 frame count, 0 byte count
2016-12-05 12:22:17.279475 GuidedMind[8705:5171369] [] nw_socket_get_input_frames recvmsg(fd 12, 1024 bytes): [57] Socket is not connected
2016-12-05 12:22:17.280004 GuidedMind[8705:5171369] [] __tcp_connection_write_eof_block_invoke Write close callback received error: [89] Operation canceled

Another thing which is notably missing from the error log is the message:

File Transfer Error: The request timed out.

I hope this information helps, if there is anything more I can do to help please let me know