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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
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