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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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