You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an app that use System.Text.Json.JsonSerializer version="8.0.0"
Found out the app when running on linux-arm mono (Debian 12) mono 6.2.x it fails to parse a simple JSON buffer.
It seems that when the JSON has valid literals it will throw an exception like this:
Unhandled exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Text.Json.JsonException: 'null}' is an invalid JSON literal. Expected the literal 'null'
The problem does not reveal on Mono Debian 16 on linux-x64 box (on a VM), Windows version also runs fine.
This is blocking us at this point since the whole point of using Mono was to deal with 32 bits architectures not supported by .NET 8.
Steps to Reproduce
internal sealed class Simple
{
public T? Property { get; set; }
}
We have an app that use System.Text.Json.JsonSerializer version="8.0.0"
Found out the app when running on linux-arm mono (Debian 12) mono 6.2.x it fails to parse a simple JSON buffer.
It seems that when the JSON has valid literals it will throw an exception like this:
Unhandled exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Text.Json.JsonException: 'null}' is an invalid JSON literal. Expected the literal 'null'
The problem does not reveal on Mono Debian 16 on linux-x64 box (on a VM), Windows version also runs fine.
This is blocking us at this point since the whole point of using Mono was to deal with 32 bits architectures not supported by .NET 8.
Steps to Reproduce
internal sealed class Simple
{
public T? Property { get; set; }
}
const string nulljson = @"{""Property"": null}";
var simple = JsonSerializer.Deserialize<Simple>(nulljson);
System.Console.WriteLine($"Simple string value:{simple!.Property}");
Our project to repro:
The text was updated successfully, but these errors were encountered: