Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.12.0
-
None
-
Using Arch Linux packages and the Bluez backend.
-
Linux/X11
-
e957470ae0e61eea1afa96d76468dbdc87168421 (qt/qtconnectivity/5.12)
Description
I use QBluetoothServiceDiscoveryAgent with both a remote device and an uuid filter (with a custom uuid for my application). Using that, I correctly get a serviceDiscovered signal with a QBluetoothServiceInfo object. However, the service uuid is null.
This causes QBluetoothSocket::connectToService to fail (as the uuid is invalid). Filling in the service uuid (which the filter should know) manually works around this issue, so the other fields seem to be okay.
Attachments
| For Gerrit Dashboard: QTBUG-72800 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 249252,3 | Ensure custom uuids are returned by QBluetoothServiceInfo::serviceUuid() | 5.12 | qt/qtconnectivity | Status: MERGED | +2 | 0 |