Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
2017.2.0b10
Issue ID
949209
Regression
No
[WSA] Unity does not add System.IO as a reference assembly when IL2CPP
Steps to reproduce:
1. Open the attached project
2. Switch platform to Windows Store
3. Build for WSA Universal 10
4. Observe the Console Window:
The type 'TextReader' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.IO, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
Actual results: Unity does not add System.IO as a reference assembly when IL2CPP
Expected results: Unity should add add System.IO as a reference assembly when IL2CPP
Reproduced with: 5.6.3p2, 2017.1.1p2, 2017.2.0b11, 2017.3.0b1
Fixed in: 2017.3.0b8, 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment