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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- "Editor unavailable" message is displayed when navigating to "Get set up" tab in Unity Hub
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
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