Unexpected character encountered while parsing value

C#Json Visual Studio-2013 json.net

C# Problem Overview

Currently, I have some issues. I'm using C# with Json.NET. The issue is that I always get:

> {"Unexpected character encountered while parsing value: e. Path '', line 0, position 0."}

So the way I'm using Json.NET is the following. I have a Class which should be saved. The class looks like this:

public class stats
{
    public string time { get; set; }
    public string value { get; set; }
}

public class ViewerStatsFormat
{
    public List<stats> viewerstats { get; set; }
    public String version { get; set; }

    public ViewerStatsFormat(bool chk)
    {
        this.viewerstats = new List<stats>();
    }
}

One object of this class will be filled and saved with:

 File.WriteAllText(tmpfile, JsonConvert.SerializeObject(current), Encoding.UTF8);

The saving part works fine and the file exists and is filled. After that the file will be read back into the class with:

try 
{ 
	ViewerStatsFormat current = JsonConvert.DeserializeObject<ViewerStatsFormat>(tmpfile);
	//otherstuff		
}
catch(Exception ex)
{
	//error loging stuff
}

Now on the current= line comes the exception:

> {"Unexpected character encountered while parsing value: e. Path '', line 0, position 0."}

I don't know why this comes. The JSON file is the following -> Click me I am the JSON link

Does anyone have any ideas?

C# Solutions

Solution 1 - C#

Possibly you are not passing JSON to DeserializeObject.

It looks like from File.WriteAllText(tmpfile,... that type of tmpfile is string that contain path to a file. JsonConvert.DeserializeObject takes JSON value, not file path - so it fails trying to convert something like @"c:\temp\fooo" - which is clearly not JSON.

Solution 2 - C#

I solved the problem with these online tools:

To check if the Json structure is OKAY: http://jsonlint.com/
To generate my Object class from my Json structure: https://www.jsonutils.com/

The simple code:

RootObject rootObj= JsonConvert.DeserializeObject<RootObject>(File.ReadAllText(pathFile));

Solution 3 - C#

In my case, the file containing JSON string had BOM. Once I removed BOM the problem was solved.

Solution 4 - C#

I experienced the same error in my Xamarin.Android solution.

I verified that my JSON was correct, and noticed that the error only appeared when I ran the app as a Release build.

It turned out that the Linker was removing a library from Newtonsoft.JSON, causing the JSON to be parsed incorrectly.

I fixed the error by adding Newtonsoft.Json to the Ignore assemblies setting in the Android Build Configuration (screen shot below)

#JSON Parsing Code static readonly JsonSerializer _serializer = new JsonSerializer(); static readonly HttpClient _client = new HttpClient();

static async Task<T> GetDataObjectFromAPI<T>(string apiUrl)
{
    using (var stream = await _client.GetStreamAsync(apiUrl).ConfigureAwait(false))
	using (var reader = new StreamReader(stream))
	using (var json = new JsonTextReader(reader))
	{
		if (json == null)
			return default(T);

		return _serializer.Deserialize<T>(json);
	}
}

#Visual Studio Mac Screenshot

#Visual Studio Screenshot

Solution 5 - C#

I have also encountered this error for a Web API (.Net Core 3.0) action that was binding to a string instead to an object or a JObject. The JSON was correct, but the binder tried to get a string from the JSON structure and failed.

So, instead of:

[HttpPost("[action]")]
public object Search([FromBody] string data)

I had to use the more specific:

[HttpPost("[action]")]
public object Search([FromBody] JObject data)

Solution 6 - C#

This issue is related to Byte Order Mark in the JSON file. JSON file is not encoded as UTF8 encoding data when saved. Using File.ReadAllText(pathFile) fix this issue.

When we are operating on Byte data and converting that to string and then passing to JsonConvert.DeserializeObject, we can use UTF32 encoding to get the string.

byte[] docBytes = File.ReadAllBytes(filePath);

string jsonString = Encoding.UTF32.GetString(docBytes);

Solution 7 - C#

I had the same problem with webapi in ASP.NET core, in my case it was because my application needs authentication, then it assigns the annotation [AllowAnonymous] and it worked.

[AllowAnonymous]
public async Task <IList <IServic >> GetServices () {
        
}

Solution 8 - C#

I ran into this issue and it ended up being because of BOM characters in my input string.

Here's what I ended up doing:

String.Trim(new char[] { '\uFEFF', '\u200B' });

This resolved the issue for me.

Solution 9 - C#

If you are using downloading data using url...may need to use

var result = client.DownloadData(url);

Solution 10 - C#

In my scenario I had a slightly different message, where the line and position were not zero.

> E. Path 'job[0].name', line 1, position 12.

This was the top Google answer for the message I quoted.

This came about because I had called a program from the Windows command line, passing JSON as a parameter.

When I reviewed the args in my program, all the double quotes got stripped. You have to reconstitute them.

I posted a solution here. Though it could probably be enhanced with a Regex.

Solution 11 - C#

I had a similar error and thought I'd answer in case anyone was having something similar. I was looping over a directory of json files and deserializing them but was getting this same error.

The problem was that it was trying to grab hidden files as well. Make sure the file you're passing in is a .json file. I'm guessing it'll handle text as well. Hope this helps.

Solution 12 - C#

In my case, I was getting an error on JsonConvert.PopulateObject(). My request was returning JSON that was wrapped in an extra pair of '[ ]' brackets, making my result an array of one object rather than just an object. Here's what I did to get inside these brackets (only for that type of model):

           T jsonResponse = new T();
                var settings = new JsonSerializerSettings
                {
                    DateParseHandling = DateParseHandling.DateTimeOffset,
                    NullValueHandling = NullValueHandling.Ignore,
                };
                var jRslt = response.Content.ReadAsStringAsync().Result;
                if (jsonResponse.GetType() == typeof(myProject.Models.myModel))
                {
                    var dobj = JsonConvert.DeserializeObject<myModel[]>(jRslt);
                    var y = dobj.First();
                    var szObj = JsonConvert.SerializeObject(y);
                    JsonConvert.PopulateObject(szObj, jsonResponse, settings);
                }
                else
                {
                    JsonConvert.PopulateObject(jRslt, jsonResponse);
                }

Solution 13 - C#

Suppose this is your json

{
  "date":"11/05/2016",
  "venue": "{\"ID\":12,\"CITY\":Delhi}"
}

if you again want deserialize venue, modify json as below

{
  "date":"11/05/2016",
  "venue": "{\"ID\":\"12\",\"CITY\":\"Delhi\"}"
}

then try to deserialize to respective class by taking the value of venue

Solution 14 - C#

I faced similar error message in Xamarin forms when sending request to webApi to get a Token,

Make sure all keys (key : value) (ex.'username', 'password', 'grant_type') in the Json file are exactly what the webApi expecting, otherwise it fires this exception.

> Unhandled Exception: Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0

Solution 15 - C#

Please check the model you shared between client and server is same. sometimes you get this error when you not updated the Api version and it returns a updated model, but you still have an old one. Sometimes you get what you serialize/deserialize is not a valid JSON.

Solution 16 - C#

This error occurs when we parse json content to model object. Json content type is string. For example: https://dotnetfiddle.net/uFClKj Some times, an api that we call may return an error. If we do not check the response status, but proceed to parse the response to model, this issue will occur.

Solution 17 - C#

In my case, it was the lack of a default parameterless constructor !!!

Solution 18 - C#

In my case, I was calling the async service method without using await, so before Task is completed I was trying to return the result!

Solution 19 - C#

I had simular problem. In my case the problem was in DateTime format. It was just numbers and it is also know as EpochFormat or UnixTimestamp. A part from my JSON:

"direction": "outbound",
"date_archive": 1554691800224,
"date_doc": 1524700800000,
"date_sent": 1524704189000,
"date_received": 1524704189000,
"date_store_till": 1712544600224,

So I've used an attribute like this:

[JsonProperty("date_received")]
[JsonConverter(typeof(MicrosecondEpochConverter))]
public DateTime? DateReceived { get; set; }

You can find MicrosecondEpochConverter code here: https://stackoverflow.com/a/19972214/4324624

Solution 20 - C#

When I encountered a similar problem, I fixed it by substituting &mode=xml for &mode=json in the request.

Content Type	Original Author	Original Content on Stackoverflow
Question	zAfLu	View Question on Stackoverflow
Solution 1 - C#	Alexei Levenkov	View Answer on Stackoverflow
Solution 2 - C#	Eduardo Pelais	View Answer on Stackoverflow
Solution 3 - C#	Aleksei Mialkin	View Answer on Stackoverflow
Solution 4 - C#	Brandon Minnick	View Answer on Stackoverflow
Solution 5 - C#	Alexei - check Codidact	View Answer on Stackoverflow
Solution 6 - C#	Praveen	View Answer on Stackoverflow
Solution 7 - C#	Celso Xavier Luz	View Answer on Stackoverflow
Solution 8 - C#	Jayesh Modha	View Answer on Stackoverflow
Solution 9 - C#	Taran	View Answer on Stackoverflow
Solution 10 - C#	JGFMK	View Answer on Stackoverflow
Solution 11 - C#	Ibaeni	View Answer on Stackoverflow
Solution 12 - C#	pkucas	View Answer on Stackoverflow
Solution 13 - C#	Hrishikesh T T	View Answer on Stackoverflow
Solution 14 - C#	A. Almazidi	View Answer on Stackoverflow
Solution 15 - C#	Nalan Madheswaran	View Answer on Stackoverflow
Solution 16 - C#	Diem Nguyen	View Answer on Stackoverflow
Solution 17 - C#	A.B.	View Answer on Stackoverflow
Solution 18 - C#	EspressoCode	View Answer on Stackoverflow
Solution 19 - C#	Vladislav	View Answer on Stackoverflow
Solution 20 - C#	AlfredBauer	View Answer on Stackoverflow