Confusing Parse Error 302

[pes-ethanp]

Writing an application for parsing JSON in string form coming via TCP.
I'm seeing a JSON parse error 302 as follows:
what(): [json.exception.type_error.302] type must be number, but is number

This is the error for multiple different JSON messages. Normally this error makes sense but this one is obviously confusing.

I tried enabling JSON_DIAGNOSTICS to see where it was popping but this causes a seg fault.

Don't know what other context would help here considering the puzzling error...

[falbrechtskirchinger]

There are only two locations where this error message could come from. Are you using nlohmann::json or are you customizing the basic_json template in any way? Have you defined any custom type conversions? Which version of the library are you using?

Meanwhile, I'll keep staring at the code to see why this might be happening.

[pes-ethanp]

Updated header file does not change outcome, unfortunately. However, I've been told by the sensor manufacturer that they'll be fixing the newline issue with the JSON message in the near future, so I probably won't be looking into this issue much further. That doesn't mean this extraction type error is addressed, so feel free to close/mark as answered/leave as is as appropriate.

Cheers.

[nlohmann]

@nlohmann Do you want me to look into that and maybe finish the PR by Sunday in time for 3.11.0?

That would be great!

[nlohmann]

@pes-ethanp Any news on this?

[falbrechtskirchinger]

FYI, PR #3548 demonstrates another way to parse multiple consecutive JSON values using iterators — no need to insert new lines into the input.

[pes-ethanp]

The sensor manufacturer published a firmware update which fixed the issue of certain JSON messages not ending with a newline character, so a conventional splitting worked just fine. Haven't had the bandwidth to go back and investigate the original parsing error any further.

[doomroep5]

Writing an application for parsing JSON in string form coming via TCP. I'm seeing a JSON parse error 302 as follows: what(): [json.exception.type_error.302] type must be number, but is number

This is the error for multiple different JSON messages. Normally this error makes sense but this one is obviously confusing.

I tried enabling JSON_DIAGNOSTICS to see where it was popping but this causes a seg fault.

Don't know what other context would help here considering the puzzling error...