Search Issue Tracker
Fixed in 2018.3.X
Votes
13
Found in
5.6.0b10
Issue ID
887128
Regression
No
[WSA] XMLSerializerException thrown when running the IL2CPP build
Steps to reproduce:
1. Open the attached project (XMLTest.zip)
2. Open the Assets/Game.unity scene
3. Switch platform to Windows Store
4. Build for WSA Universal 10 SDK (IL2CPP backend), Build type - XAML
5. Open Visual Studio solution
6. Deploy on local machine (Debug or Release)
7. Observe the errors in the Output console
Expected result: Errors should not appear in the Output console
Actual result: Errors appear in the Output console
Note:
Not reproducible with Master mode
Reproduced with: 5.6.0b10, 5.6.0b11, 2017.1.0a2
Not reproduced with: 5.4.5f1, 5.5.2p2
Fixed in: 2018.3.0a11 (on .NET Standard 2.0 Api Compatibility Level)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
JoshPeterson
Jun 06, 2018 11:56
The problem here is managed code in System.Xml.dll that does not place nicely with an AOT compiler (like IL2CPP).
We've corrected this issue in 2018.1 and 2018.2. In those versions of Unity, you will need to use the .Net Standard 2.0 Api Compatibility Level to get the AOT-friendly version of System.Xml.dll. In Unity 2018.3 we will also have an AOT-friendly version of System.Xml.dll for the .NET 4.x Api Compatibility Level.
I'm not sure why I marked this as Won't Fix - that was an error. Sorry!
sailoralex
Jan 24, 2018 10:31
this bug is still there in 2017.3.0f3
Siyka
Oct 30, 2017 15:58
Six months later still not fixed. 2017.2. We cannot update any of our games for Windows. The alternative .NET build has other issues. Shall we give up using Unity?
Jabbah76
Apr 25, 2017 07:07
Unfortunately for me, this bug is also reproducible in Master mode.
Mathijs333
Apr 25, 2017 06:50
Also reproduced in master mode.
This withhold us from publishing because of other bugs in 5.5.2, so please, could this get a higher prio?