FWIW, while i don’t understand the excact problem, as the sample you provided does not have any slashes I can see, this fix seems fundamentally bad/wrong. quotes inside string literals will need escaping, e.g.
Hi Marc,
The problem is RO add to json labels the (") string. have no idea why. Then the parser add escape to everything, including the " in the labels.
The initial and ending quotes are added for the parser, not in the original string. The original string is an output from the ro json parser, btw.
The original string , adding quotes to label, is the output of RO json parser and is unnecessary and a problem , actually, because this is the only cause of slashes to escape. The only quote required is a string data in json
Then I guess more context is needed for where this is happening? Whoever adds the surrounding quotes is also (rightfully) adding the escaping. Dropping the escaping for quotes is not the right fix. the question is, who is re-quoting your Json message string… there’s zero context in your post to go on, for that…