Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.2.0a3
Issue ID
919294
Regression
Yes
INVALID_UTF8_STRING error in the Font Names field when upgrading a project to 2017.2
Steps to reproduce:
1. Open the attached project (UnityTest.zip)
2. In the Assets folder click on "arialbd"
3.Observe the error in the Font Names field
INVALID_UTF8_STRING
Expected result: Font Names should be shown
Actual result: Error in the Font Names field
Reproduced with: 2017.2.0a1, 2017.2.0a2, 2017.2.0a3
Not reproduced with: 5.4.5p3, 5.5.3f1, 5.5.4f1, 5.6.1p3, 2017.1.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The text, buttons and checkmarks are outside their visual bounds when the Tier Settings window is docked
- Invalid front face configuration when building with GraphicsAPI set to WebGPU
- WebGL builds report wrong screen resolution if "matchWebGLToCanvasSize" is set to "false"
- List<T> in the Inspector does not update values when changed through Dropdown menu
- Crash on keywords::LocalSpace::Find when reimporting specific assets
Add comment