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
- [Backport] Instanced URP Shaders using Spherical harmonics variables causes long initial mesh render time when used in WebGL
- Stopped Audio Souce outputs audio when the "Spatialize" property is enabled
- Preset Manager does not apply to Terrain creation
- [VFX Graph] Errors are thrown when renamed graph is focused after exiting Play Mode
- Build fails with errors "Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly" when URP is included in UWP Build
mayasarii876
Mar 09, 2022 04:53
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
shubhamswaraj2021
Aug 18, 2020 11:30
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
JPoenisch
May 14, 2019 07:48
Apparently this Bug still exists in Unity 2018.3.14 ... still the only thing working is switching to compatibility level ".Net Standard 2.0" ... exception is thrown for
```
var serializer = new XmlSerializer(typeof(SomeType));
```
exception:
System.ArgumentException: 'CP1252' is not supported encoding name.
Fiedel
May 14, 2019 07:45
This issue appears to persist in Unity 2018.3.14
YoloJero
Mar 25, 2019 15:37
Still had this issue in 2018.3.4f1 with Api Compatibility Level .Net 4.x
Switching to .Net Standard 2.0 (still throws an exception but) worked for me.
nilsubimax
Oct 29, 2018 15:40
Seems to be still open for 2018.3.0b6 with .NET 4.6 enabled. I think this should not only be fixed for a specific framework, but for all available frameworks. Could you please reopen this issue so that we can cast votes again?
Arctous
Sep 13, 2018 20:53
@JOSHPETERSON
I see that 2018.3b was released for beta. However, this issue is not mentioned in the release notes. Is this fixed?
Mgravitus
Aug 06, 2018 15:02
So which version of Unity is this fixed for IL2CPP?
Arctous
Jul 26, 2018 23:52
Just upgraded to 2018.2.1f1. I confirmed that the System.XML.Serialization issue is fixed under 2018.2.1f1 under the ".NET Standard 2.0" selection in the "API Compatibility Level" setting.
Arctous
Jul 26, 2018 22:20
@joshpeterson - I am currently using 2018.1. Is there a release date for the 2018.3 beta? I am also using System.Xml.Serialization and have the same output as @cruelbob. I am unable to run on iOS and release to my testers because of this error.