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)
Comments (15)
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
- “FocusController has unprocessed focus events.” warnings are thrown after adding iOS, tvOS or visionOS Build Profiles
- Holes and different colors appear on default Tree Materials after applying them to the Tree GameObject and undoing changes
- Error indicating that the Text Asset Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
- Documentation installation shows "Install failed: Validation Failed" when installing Android Build Support module
- Error indicating that the Package Manifest Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
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?