Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
909364
Regression
Yes
The .meta file generated for the .DLL plugins do not respect the YAML specifications
Steps to reproduce:
1. Create a new project
2. Import any DLL
3. Open the meta file of DLL
4. Observe, the .meta file generated for .DLL plugin does not respect the YAML specifications
Expected result: The content of a mapping node is an unordered set of key (Excerpt from http://yaml.org/spec/1.1/)
Actual result: The content of a mapping data includes duplicate "data" keys under "platformData", which is illegal according to the specification.
Reproduced with: 5.5.3p3, 5.6.1f1, 5.6.1p1, 2017.1.0b6
Not reproduced with: 5.3.8f1, 5.4.5p2
Fixed in:
2017.2.0b2
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