nRFConnect for desktop - attr value Hex vs. Text

[eyalasko]

Hi,

Using nRFConnect for desktop I've noticed that when writing an attribute I usually enter the hex values of a byte array (e.g. "12" = 0x12) but on other occasions the values sent are actual characters typed (e.g. typing "12" actually sends equivalent ascii values "31 32")

Can someone elaborate on what occasions the input field is considered text vs hex values?

Thanks

[Hung Bui]

Hi Eyalasko, 

It's quite strange to hear about the bug. How often do you see the bug ? Could you send us the log or screen shot when you see the bug ? 

[eyalasko]

Hi,

Its getting even stranger -

The attribute is 42 bytes long.

Right after establishing a connection I send the (not allowed) sequence 'XYZ' and its being written to offset 22 (zero based)

When sending the same sequence after reading the attribute, its being written to offset 42 (zero based)

See attached screen cap

[Hung Bui]

Hi Eyalasko, 
It's quite strange that you can input XYZ into the text box. It's supposed to accept only hexadecimal characters. I assume the application was not modified ? How often do you see the issue ? 

Could you let us know your environment ? Operating system ?

[eyalasko]

Hi Hung Bui

Its Windows 10 system.See attached system reports

The app was downloaded, not built hence no modifications.

Its the 1st time I see it and it happens only (as I've observed) on this characteristic/attribute. along with other strange behavior described above.

[Hung Bui]

If possible could you give us an example that we can run here on the nRF52 to reproduce the issue ? 

Is there anything special about the characteristic declaration ? 

[eyalasko]

I don't think there's anything special with the characteristic (other than being a long one) as it works as expected with nRFConnect Android app.