Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4.0f1
2021.1
Issue ID
1281011
Regression
No
Unable to parse file error is thrown when importing specific Prefab
Reproduction steps:
1. Create new empty Project
2. Import attached Prefab "CorruptedPrefab"
3. Try to open the imported Prefab
Expected result: Prefab is imported properly
Actual result: "Unable to parse file" error is thrown at line "m_SourcePrefab: {fileID: 100100000, guid: 7d03946ef08e8b54eac96b14f608af3d, type: 3}"
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.10f1, 2020.2.0b9, 2021.1.0a2
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
- 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
Resolution Note (2021.2.X):
Unity YAML is a subset of the YAML spec for performance. Unity YAML does not serialize using inline[]. We do not support loading externally modified files.