Search Issue Tracker
Fixed in 5.6.0
Votes
12
Found in
5.3.0b5
Issue ID
742049
Regression
No
Windows Store: IL2CPP does not support plugins targeting .NET 4.0+ or referencing Windows Runtime
At this point in time, using IL2CPP scripting backend on Windows Store limits your assemblies to targeting up to .NET 3.5 (the same limit that applies to all other Unity platforms including the editor). Trying to use DLLs compiled against .NET 4.0 or higher or DLLs that reference .winmd files (i.e. Windows Runtime APIs) will cause build to fail by UnusedBytecodeStripper2.exe crashing with one of the following errors:
AssemblyResolutionException: Failed to resolve assembly: 'System.Runtime, Version=4.0.20.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
AssemblyResolutionException: Failed to resolve assembly: 'Windows, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null'
The only workaround is marking these plugins as not compatible with Windows Store IL2CPP scripting backend.
Comments (1)
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
- ShadowCaster2D shadow flickers in the Editor's Scene and Game Views when Tilemap Shadow Caster's Casting Source is set to Tilemap Collider 2D
- The "all=" prefix is dropped from the Entities Hierarchy search box when a component is selected from the autocomplete drop-down
- Scene and Game views become progressively blurrier each time "Standard” Sub Scene Asset is reimported
- Render Mode does not fall back to "Multi-pass" if "Single Pass Instanced" is unsupported when building project to iOS with MockHMD plugin
- GameObjects' scaling is distorted during Play mode when their Animator component is active
IsmaeelShujat
Oct 12, 2017 11:32
exception Failed to resolve assembly: 'System.Runtime, Version=4.0.20.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Not resolved in Unity5.6.2f1....
Please update...