Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.2
-
None
-
-
8
-
30390a1285 (qt/qtconnectivity/dev) 30390a1285 (qt/tqtc-qtconnectivity/dev) 228d5bad4b (qt/tqtc-qtconnectivity/5.15) 7a7b4da687 (qt/qtconnectivity/6.2) 0834e23775 (qt/qtconnectivity/6.3) 7a7b4da687 (qt/tqtc-qtconnectivity/6.2)
-
Team One Foundation Sprint 50
Description
QBluetoothServiceDiscoveryAgent first discovers devices, and once the devices has been scanned, it scans these devices for their services (SDP).
However with Windows client only the last discovered device is scanned for services.
This is because then the service scan starts, it first goes off with:
QBluetoothServiceDiscoveryAgentPrivate::startServiceDiscovery() ... start(discoveredDevices.at(0).address());
And later once that service scan is ready, it should go on to scan the next device's services. However, with Windows the slot to do this
QBluetoothServiceDiscoveryAgentPrivate::_q_serviceDiscoveryFinished()
Is not connected to the finished signal and the next scan does not start. To make matters a bit worse, the public-facing service-scan ready signal is emitted and the user gets an indication that all has been scanned.