Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b7
Issue ID
1002678
Regression
No
[UWP] Using .NET Standard 2.0 libraries AssemblyConverter fails with NullReferenceException when building UWP project
How to reproduce:
1. Download attached project file and open "Test" Scene
2. Build a Visual Studio solution for the UWP
3. Build the resulting Visual Studio solution
Actual result: Using .NET Standard 2.0 libraries, exported Visual Studio Solution fails to build due to an exception of the AssemblyConverter. The libraries work correctly within the Unity Editor and on other platforms
Why won't fix: Unity does not support .NET Standard 2.0 on UWP with .NET scripting backend. It's only supported on IL2CPP scripting backend.
Reproduced with: 2018.1.0b8, 2018.2.0a1
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
Add comment