Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.7.0
-
None
-
Embedded Linux on ARM for Gatt Service.
Description
If I use a custom 128 bit service uuid it does not end up in the advertisement data for the GATT Server.
advertisingData.setServices(QList<QBluetoothUuid>() << QBluetoothUuid(QStringLiteral("73b0d2d0-4ddd-460c-aa93-625259f8eb3a")));
If I use a 16 bit one it does work.
advertisingData.setServices(QList<QBluetoothUuid>() << QBluetoothUuid(quint16(0x2000)));
I can interrogate and use the service but I need to be able to see what service(s) are available in the advertisement so I don't waste a lot of time looking.
Not sure if this relates to endian issues reported earlier in
QTBUG-53421