Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.11.0 Beta 3
-
None
-
Win10, Windows Phone 10, VS 2015
-
WinRT
Description
With the current 5.11 git branch (03-April-2018) networking on WinRT is broken. For instance the socket test code from https://bugreports.qt.io/browse/QTBUG-61078 produces this output:
Socket state: QAbstractSocket::ConnectedState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState Timeout Socket state: QAbstractSocket::UnconnectedState Got data: 0 requestData() Socket state: QAbstractSocket::ConnectingState Socket state: QAbstractSocket::ConnectedState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState Timeout Socket state: QAbstractSocket::UnconnectedState Got data: 0 requestData() Socket state: QAbstractSocket::ConnectingState Socket state: QAbstractSocket::ConnectedState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState Timeout Socket state: QAbstractSocket::UnconnectedState Got data: 0 requestData() Socket state: QAbstractSocket::ConnectingState Socket state: QAbstractSocket::ConnectedState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState Timeout Socket state: QAbstractSocket::UnconnectedState Got data: 497 requestData() Socket state: QAbstractSocket::ConnectingState Socket state: QAbstractSocket::ConnectedState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState QNativeSocketEngine::bytesAvailable() was called in QAbstractSocket::UnconnectedState QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState
Also HTTP requests using the QNetworkAccessManager fail/stall most of the time. Maybe this is related to the bug: https://bugreports.qt.io/browse/QTBUG-65556 ?
Pure QTcpSockets worked fine with the Qt 5.11 Beta 2 release (from the Maintenance tool installer).