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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
The version number should be present for .NET Standard 2.1.