nRF-Connect Windows Advertising issues

RE: nRF-Connect Windows Advertising issues

Sigurd — Tue, 09 May 2017 09:01:34 GMT

Hi,

That is correct. I have updated my answer.

Michael Portmann — Mon, 08 May 2017 23:50:04 GMT

Hi,

I think the bug is actually the 20 byte limit. The advertising packet can contain upto 31 characters. (BLE_GAP_ADV_MAX_SIZE)

Sigurd — Mon, 08 May 2017 14:28:19 GMT

Hi,

Thank you for reporting this. There seem to be 2 different bugs here.

It's only possible to add one Custom AD type to the advertising data. When adding a second Custom AD type the first one will be overwritten. Only the one added last will be included.
The 20 bytes limit. This should have been 31 bytes.

Both bugs have been reported internally, and will hopefully be fixed in the next release.