Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0b9
2019.2.0a1
Issue ID
1142324
Regression
No
JsonUtility.FromJson(string) throws a JSON parse error when string contains Byte Order Mark
1. Open the attached project from "2019_1_JsonUtility.zip"
2. Open and Play the "SampleScene"
Expected: JsonUtility.FromJson() correctly parses the information
Actual: JsonUtility.FromJson() throws a JSON parse error in the Console
Reproduces on: 2017.4.25f1, 2018.3.12f1, 2019.1.0b10, 2019.2.0a10
Note:
- Some input methods filter out Byte Order Marks, such as File.ReadAllText(), which can be an effective workaround when working with local files
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
JsonUtility.FromJson() is made with the expectation that the string that is passed as a parameter would be composed of just the characters and would not contain any Byte Order Marks