additional non-parsable characters are at the end of the string. c#

Question

Below is the piece of my code which is throwing ex two exception in this line and I have no clue whats wrong in here.

Exceptions thrown are:

1. JsonReaderException: Input string '08' is not a valid number. Path 'Ape', line 1, position 51.
2. FormatException: Additional non-parsable characters are at the end of the string.

The Json which I am deserializing line by line is as follows:

{"PartitionKey": "test","RowKey": "first","Ape": 06,"Nepe": "depe","EPA": 323,"Time": "04/23/2012 18:25:43","bits": "test"}
{"PartitionKey": "test","RowKey": "Second","Ape": 107,"Nepe": "TNepe","EPA": 23,"Time": "04/22/2012 18:25:43","bits": "Ttest"}
{"PartitionKey": "test","RowKey": "Third","Ape": 08,"Nepe": "TNepe","EPA": 34,"Time": "04/20/2020 18:25:43","bits": "Jtest"}

There is no problem in reading first two line but error happens at third/last line. I am not sure as what is wrong as I made sure no extra space in middle or end of line and 'Ape' key is of type integer.

here is my code>, the error occurs at Deserializing Json Object. Find the value passed in line before error occurs in the screen shot>

foreach( var line in lines )
        {
            var data = JsonConvert.DeserializeObject<JObject>( line );
            var errors = validator.Validate( data, schema );
            
            if( errors.Count() > 0 )
            {...

Please let me if one knows whats wrong and the fix required. Thanks

Answer 1

I have a line where it reads with leading zero but throws error for next line and that is my whole question here

If this is the question the answer is simple, Json.Net is reading it as an octal

The octal numeral system, or oct for short, is the base-8 number system, and uses the digits 0 to 7.

So anything with a leading 0 it will consider an octal

For instance, it will parse 03, but it will not parse (and throw an error) on 09

You may even get the right results for 00 - 07. However, if you had 077 (although it will parse) you will get a value of 323, which will most likely not be what you want or you would expect.

Example

77 = int == 77
077 = octal = 323
63 = int = 63
010 = octal = 8
8 = int = 8
9 = int = 9
08 = octal = throw
09 = octal = throw

In short, the json is malformed, you will likely need to fix this at the source. or fix the json before you parse it

Answer 2

If you put your JSON on this url: https://jsonformatter.curiousconcept.com/# you can see the error that occours in your case, is the integer starting with zeros.
The better explanation you can find in this question: https://stackoverflow.com/questions/27361565/why-is-json-invalid-if-an-integer-begins-with-a-leading-zero#:~:text=6%20Answers&text=A%20leading%200%20indicates%20an,would%20not%20contain%20an%208.

Answer 3

I used this JSON validator https://jsonformatter.curiousconcept.com
and it seems there are 2 problems here:
1st: There are 3 root object elements
2nd: Numbers can't start with 0

I believe this is the structure you seek:

[{
    "PartitionKey": "test",
    "RowKey": "first",
    "Ape": 6,
    "Nepe": "depe",
    "EPA": 323,
    "Time": "04/23/2012 18:25:43",
    "bits": "test"
}, {
    "PartitionKey": "test",
    "RowKey": "Second",
    "Ape": 107,
    "Nepe": "TNepe",
    "EPA": 23,
    "Time": "04/22/2012 18:25:43",
    "bits": "Ttest"
}, {
    "PartitionKey": "test",
    "RowKey": "Third",
    "Ape": 8,
    "Nepe": "TNepe",
    "EPA": 34,
    "Time": "04/20/2020 18:25:43",
    "bits": "Jtest"
}]