System. Text. Json. Jsonexception: the Input Does Not Contain Any Json Tokens

Another reason this error could pop up, as it did for me, is simply because the API endpoint doesn't exist because it was misspelled.

I got a similar error in Program.cs Main method CreateHostBuilder(args).Build();:

System.FormatException: 'Could not parse the JSON file.'

JsonReaderException: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. LineNumber: 0 | BytePositionInLine: 0.

For me it turned out to be the local secrets.json file that not contained a valid json object.

Because of this I could not see any errors in Git or rollback to a working commit since the file is not checked in.

Solved by adding an empty object to the file via Visual Studio - right click the project in solution explorer and select Manage User Secrets:

{

}

In my case the code was doing this:

var json = await response.Content.ReadAsStringAsync();
var result = JsonObject.Parse(json); // threw the exception mentioned in the question

Why did that happen? That's because json value was an empty string "". Parse fails with an empty string.

Fixed it doing this simple change:

var json = await response.Content.ReadAsStringAsync();
var result = string.IsNullOrEmpty(json) ? null : JsonObject.Parse(json);

i had similar issue and the problem to check if the json string you are readying is empty, null, or bad formatted. debug to the code line where you are reading data into string before deserialize or serialize call.

I was also having the same error in this line: CreateWebHostBuilder(args).Build().Run();.

The solution is to right click on your project file in Visual Studio, select the option manage secret file and if that file (secret.json) is empty then put {} into that file.

For me, this error occurred when calling FindByNameAsync of UserManager.

Sounds silly, but the database connection string in the appsettings was wrong!

I got this error when communicating between two APIs.

request = await req.DeserializeRequestBodyAsync<MyDto>(jsonSerializerOptions);

Turned out the code below did not actually send any values:

httpRequestMessage.Content = JsonContent.Create(myDto);
var httpClient = _clientFactory.CreateClient();
var httpResponseMessage = await httpClient.SendAsync(httpRequestMessage, cancellationToken);

I had to manually specify:

await httpRequestMessage.Content.LoadIntoBufferAsync();

Like this:

httpRequestMessage.Content = JsonContent.Create(myDto);
await httpRequestMessage.Content.LoadIntoBufferAsync();
var httpClient = _clientFactory.CreateClient();
var httpResponseMessage = await httpClient.SendAsync(httpRequestMessage, cancellationToken);

Late answer - but I ran into this using Blazor WebAssembly with Browser Link (trying to get Hot Reload to work). Turns out it's an issue loading the appsettings and Browser Link was expecting the secrets file. I fixed by right clicking the Server project and copy/pasting my appsettings values into the secrets file.

In my case, I was passing the id of my object along with the object itself in the url of the put request to an API and faced the same exception. It turned out that it was not necessary to pass the id (as it was retrieved from the object itself, in fact it was not present in the method signature). Removing the id solved the problem.

This error occurred when communicating between client and web API.

API code:

public async Task<IActionResult> PostAsync(object review)
{
    return Ok();
}

Client code:

var res = await _client.PostAsJsonAsync("api/reviews", review);
if (res.IsSuccessStatusCode)
{
    var myObject = await res.Content.ReadFromJsonAsync<MyObject>(); //this line threw mentioned error
}

Turned out that the API endpoint was returning something different compared to what I was trying to read from JSON i.e. I was trying to read MyObject but API was returning ActionResult

In my case database column was marked not null and I was passing null in API.

I was missing a comma (,) at the end of a line in appsettings.json

In my case we were missing Content-Length header our request, which should be the length of your json input

Got this error because I did not have access to the endpoint.