Device advertising a 128-bit service UUID is not discovered by the nRF Toolbox scan operationhttps://devzone.nordicsemi.com/f/nordic-q-a/37190/device-advertising-a-128-bit-service-uuid-is-not-discovered-by-the-nrf-toolbox-scan-operationnRF Toolbox scanner code does not seem to discover devices which advertise a 128-bit service UUID. I have extended the Template app (within nRF Toolbox) to interact with my BLE device which advertises a custom 128-bit service UUID (complete list, ADen-USTelligent Community 13Wed, 08 Aug 2018 09:49:15 GMTRE: Device advertising a 128-bit service UUID is not discovered by the nRF Toolbox scan operationhttps://devzone.nordicsemi.com/thread/143330?ContentTypeID=1Wed, 08 Aug 2018 09:49:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d5a5bce7-e024-4d20-b8a6-fe9d1aff36eeAcutetech<p>Hmmm... This was my bug - sorry.</p> <p>Details: when I used the 128-bit service UUID I placed the wrong value in the advertising data, even though the correct value was in the GATT database. That explains why (a) my device was not found during scanning for advertisments but (b) why it would work OK once my device was present in the Bonded Devices list (since the advertisments were not checked, but the service discovery found the expected service).</p> <p>When I used the 16-bit service UUID I placed the correct data in the advertisment data and the scan found my device. So it appeared like a problem with the phone scanning 128-bit UUIDs, but the real bug was in the contents of the 128-bit advertising data.</p><div style="clear:both;"></div>