Unable to parse valid JSON

Question

Unable to parse valid JSON

Closed this issue 7 years ago · 8 comments

I have a valid JSON string (according to RFC 4627, RFC 7159, ECMA-404):

{"code":0,"message":"OK","result":[{"fund_id":2,"fund_mnemo":"BAIKAL","fund_name":"\u041e\u0410\u041e \u0410\u041a \"\u0411\u0430\u0439\u043a\u0430\u043b\u0411\u0430\u043d\u043a\" ","allow":true,"answer":"\u041d\u0435\u0442 API \u0444\u043e\u043d\u0434\u0430"},{"fund_id":4,"fund_mnemo":null,"fund_name":"\u041f\u0440\u0435\u0437\u0435\u043d\u0442\u0430\u0446\u0438\u043e\u043d\u043d\u044b\u0439 \u0444\u043e\u043d\u0434","allow":true,"answer":"\u041d\u0435\u0442 API \u0444\u043e\u043d\u0434\u0430"}],"cached":false}

but mozilla extension says

bad Unicode escape at line 1 column 126 and shows raw string without formatting.

Any other parsers can parse it, tested at:
https://jsonformatter.curiousconcept.com/
http://codebeautify.org/jsonviewer
http://www.jsoneditoronline.org/

Answer 1 · 2017-01-16T17:23:54.000Z

Thanks, I'll take a look

…

-Ben

On Jan 16, 2017, at 5:06 AM, Aleksandr.ru ***@***.***> wrote: I have a valid JSON string (according to RFC 4627, RFC 7159, ECMA-404): {"code":0,"message":"OK","result":[{"fund_id":2,"fund_mnemo":"BAIKAL","fund_name":"\u041e\u0410\u041e \u0410\u041a \"\u0411\u0430\u0439\u043a\u0430\u043b\u0411\u0430\u043d\u043a\" ","allow":true,"answer":"\u041d\u0435\u0442 API \u0444\u043e\u043d\u0434\u0430"},{"fund_id":4,"fund_mnemo":null,"fund_name":"\u041f\u0440\u0435\u0437\u0435\u043d\u0442\u0430\u0446\u0438\u043e\u043d\u043d\u044b\u0439 \u0444\u043e\u043d\u0434","allow":true,"answer":"\u041d\u0435\u0442 API \u0444\u043e\u043d\u0434\u0430"}],"cached":false} but mozilla extension says bad Unicode escape at line 1 column 126 and shows raw string without formatting. Any other parsers can parse it, tested at: https://jsonformatter.curiousconcept.com/ http://codebeautify.org/jsonviewer http://www.jsoneditoronline.org/ ― You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 2 · 2017-01-16T17:33:39.000Z

I'm seeing false parsing errors as well, seems to be an interesting combination of escaped values and numbers.
JSONView 1.2.2 c/o Firefox

Simple snippet to reproduce:

{
    "precondition": "text that ends in an escaped backslash \\",
    "errorline": "After the number, the parser complains: 3 here is the error"
}

expected ',' or '}' after property value in object at line 3 column 61

@Aleksandr-ru if I open your string with JSONView it doesn't complain, though.

(edit: typo)

Answer 3 · 2017-01-16T19:01:00.000Z

Potentially the same problem. Parse is failing on:

{
   "key":"\"value\u201d"
}

Answer 4 · 2017-01-16T23:59:27.000Z

Thanks for all the examples! I should be able to bang out a fix pretty quick.

Answer 5 · 2017-01-17T00:08:19.000Z

@alpha0010 that example works for me with JSONView 1.2.2.

Answer 6 · 2017-01-17T00:08:52.000Z

@Aleksandr-ru your example also works in JSONView 1.2.2.

Answer 7 · 2017-01-17T00:11:58.000Z

@elgrafico your problem was a bug caused by a really stupid typo. I'll push JSONView 1.2.3 soon.

Answer 8 · 2017-01-19T22:31:31.000Z

Not sure why mine was not worker before then... but in any case, it works now. Thanks for the fast response.