Different byte order in nRF Connect 2.0 iOS App and nRF Connect v3.1.0 for Desktop

[hannes]

In an BLE example I have a characteristic with the value 0x00001234. In the nRF Connect 2.0 for iOS i see the value 0x00001234 and in nRF Connect for Desktop v3.1 i see "34 12 00 00".  Also when I enable Notification the log says "[...] INFO Attribute value changed, handle: 0x12, value (0x): 34-12-00-00" It's always the same example without any changes to the code. Is there a possibility to change the byte order or is this for some reason?

[Dinesh Harjani]

Hi hannes

Developer for nRF Connect for iOS speaking, here. Thank you very much for filing this bug report, we were able to fix it and put it in our upcoming 2.0.2 bug-fix release, which we expect to have ready by the end of this week or early next week.

Thank you very much for your support !

[hannes]

Thank's for the feedback! Looking forward to the update ;-)