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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment