Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.6, 5.7, 5.8
-
None
Description
It's possible to create a QBluetoothSocket with 'UnknownProtocol' type and then continue with connectToService. On OS X (for example) this results in UnknownError instead of documented/expected UknownProtocolError. Also, it's possible to call overloaded connectToService and this will result in undesired device discovery (undesired, since we'll fail to connect after all).
Attachments
| For Gerrit Dashboard: QTBUG-55073 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 166639,5 | QBluetoothSocket::connectToService - check a socket type first | 5.6 | qt/qtconnectivity | Status: MERGED | -2 | 0 |
| 166701,2 | QBluetoothSocket::connectToService - check a socket type first | dev | qt/qtconnectivity | Status: ABANDONED | -2 | 0 |