Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.3
2020.3.2f1
2021.1
2021.2
Issue ID
1325890
Regression
No
Incorrect formatting in plugin metafile after modifying plugin platform settings
Reproduction steps:
1. Open the user's attached project "assembly-meta-bug.zip"
2. In the Project window under "Assets/Plugins" select "Newtonsoft.Json.dll"
3. In the Inspector window set "Select platforms for plugin" > "Exclude Platforms" > "Editor" > True
4. Click "Apply"
5. Open the "Newtonsoft.Json.dll" file in windows explorer
6. Open the aforementioned file's metafile in a text editor
Expected result: line 15 of the metafile should read like this "Any: "
Actual result: line 15 of the metafile reads like this ": Any "
Reproduces on: 2018.4.33f1, 2019.4.23f1, 2020.3.2f1, 2021.1.2f1, 2021.2.0a12
Notes:
-In 2018.4.33f1 line 15 of the metafile is " ' ': Any "
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (2021.2.X):
I tried to work around the issue by patching the serialization method in the Plugin importer but the owners of that code are rejecting the changes. The justification is that this does not solve the general issue ( this can happen anywhere a Dictionary is serialized.) but adds code debt that can't ever be reverted. The issue can't be fixed at the serialization level without introducing a performance regression that would affect all Yaml files parsing. As stated in the documentation, UnityYAML does not follow the YAML specification so parsing the YAML with an external reader is just not guaranteed to work. For those reasons, I'm afraid I have to resolve this issue as 'By Design'.