Socket.read(...) unexpectedly returns 0 about bluesslservice HOT 3 OPEN

This is still an issue and the potential fix still works, just ran into it attempting to read 90k bytes from an android client.

from bluesslservice.

Are you sure the socket is blocking? EWOULDBLOCK should only return for a non-blocking socket.

from bluesslservice.

Yes, the socket is definitely configured to be blocking (isBlocking in Socket.swift).

EWOULDBLOCK is being raised in the SSL layer upon reading at least one byte but fewer bytes than requested. Excerpts from SSLService.swift:

	private func sslReadCallback(...) -> OSStatus {
		...
		// Read the data from the socket...
		let bytesRead = read(socketfd, data, bytesRequested)
		if bytesRead > 0 {
			
			dataLength.initialize(to: bytesRead)
			if bytesRequested > bytesRead {
				
				return OSStatus(errSSLWouldBlock)
				
			} else {
				
				return noErr
			}
		...
	}

	public func recv(...) throws -> Int {
		...
				if status == errSSLWouldBlock {
				
					errno = EWOULDBLOCK
					return -1
				}
		...
	}

from bluesslservice.