Search Issue Tracker
By Design
Votes
0
Found in
2021.2.0b15
2022.1.0a12
2022.1.0a14
Issue ID
1378144
Regression
Yes
Api Compatibility Level contains version number for .NET Standard
How to reproduce:
1. Create a new Unity project
2. Open Player settings
3. Other Settings -> Configuration -> Api Compatibility Level
Expected result: There are two choices - .NET Standard & .NET Framework, version numbers should not be included.
Actual result: There are two choices - .NET Standard 2.1 & .NET Framework. Version number from .NET Standard 2.1 should be removed.
Reproduced with: 2022.1.0a14, 2022.1.0a12, 2021.2.1f1, 2021.2.0b15.
Didn't reproduce with: 2022.1.0a11, 2021.2.0b14.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
The version number should be present for .NET Standard 2.1.