Search Issue Tracker
Fixed in 2017.2
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
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
- 2019.4: PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
Add comment