Reading NFC record under 4 chars causes weird issues.

RE: Reading NFC record under 4 chars causes weird issues.

Jared — Tue, 26 Oct 2021 13:47:59 GMT

Hi,

It shouldn't be necessary to remove the header by subtracting 3 as payload_desc->payload_length variable contains the actual payload length without the header. You also don't need to add 3 for original_message pointer as it already points at the start of the payload.

The SDK parsing functions should parse it correctly regardless if "record length" field is 4-byte or 1-byte record.

regards

Jared

RE: Reading NFC record under 4 chars causes weird issues.

Jared — Fri, 22 Oct 2021 13:47:25 GMT

Hi there,

I have to discuss this with our developers.

I will be back with more sometime next week.

regards

Jared

RE: Reading NFC record under 4 chars causes weird issues.

NathHorrigan — Wed, 20 Oct 2021 13:19:28 GMT

This is what it looks like for the first two. To me it all looks okay?

RE: Reading NFC record under 4 chars causes weird issues.

NathHorrigan — Wed, 20 Oct 2021 13:03:59 GMT

Hi Jared!

FYI I use VSCode but here is the payload:

RE: Reading NFC record under 4 chars causes weird issues.

Jared — Wed, 20 Oct 2021 12:59:25 GMT

Hi,

If you use the debugger and set a breakpoint in line 29 before you format the payload, and add payload_desc->payload to "watch" in SES. How does payload_desc->payload look like in debug view for the "A" case? Can you see the header + the whole payload?

regards

Jared