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
- 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:
The version number should be present for .NET Standard 2.1.