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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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...