Existing code base suddenly fails on a QBluetoothSocket::connectToService() call after upgrading to Qt 5.12.0. The core is basically nothing more than:
This results in a message in the console: Connecting to port is not supported (Uuid required) . Up to now, I did not find any documentation telling that this is not supported any more. This, I consider part 1) of this issue.
Ok, then I adapted the above code to use an uuid. No service scan is done (we know what to connect to), and the used uuid is the well known Bluetooth SSP one. Running this fails immediately with the message:
QDBusPendingReply: type ManagedObjectList is not registered with QtDBus. I verified this in Qt's source code, and see that the
call is only in the file bluez5_helper.cpp in the function
Verified that in this scenario (no scan for BT addresses or services), indeed the ManagedObjectList is not registered, so the console message is valid. Further, when I force a scan for BT addresses I see that the ManagedObjectList is properly registered, and a subsequent connectToService() succeeds. When this is intended behavior, this needs to be documented, but this does not feel like intended behavior to me. This, I consider part 2) of this issue.
|For Gerrit Dashboard: QTBUG-72742|
|248981,2||Add missing dbus registrations and change documentation||5.12||qt/qtconnectivity||Status: MERGED||+2||0|