Search Issue Tracker
By Design
Votes
4
Found in
2018.2.0f2
Issue ID
1067823
Regression
No
Uanble to build when PiXYZ Unity Plugin is added because of "mscorlib" may not be referenced
How to reproduce:
1. Open user attached project
2. Build it (Files > Build Settings > Build & Run)
3. Observe Console
Expected results: The project will be successfully built
Actual results: Build fails because of an error "ArgumentException: The Assembly mscorlib is referenced by UnityEngine.CoreModule"
Reproduced: 2017.1.5f1, 2017.2.3p3, 2017.3.1p4 2017.4.8f1, 2018.1.9f1, 2018.2.3f1, 2018.3.0a8
Note:
Issue disappears after changing Scripting Runtime Version from .NET 4.x to .NET 3.5
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Change Assets\PiXYZ\Editor\PiXYZImportMenu.cs
PlayerSettings.SetApiCompatibilityLevel(report.summary.platformGroup, ApiCompatibilityLevel.NET_2_0);
to
if (EditorApplication.scriptingRuntimeVersion == ScriptingRuntimeVersion.Legacy)
PlayerSettings.SetApiCompatibilityLevel(report.summary.platformGroup, ApiCompatibilityLevel.NET_2_0);
else
PlayerSettings.SetApiCompatibilityLevel(report.summary.platformGroup, ApiCompatibilityLevel.NET_4_6);