Search Issue Tracker
Fixed in 0.1.2
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1091889
Regression
No
[UWP] Ambiguous references when using Scripting Runtime Version 4.x Equivalent
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/159
Reproduction Steps:
1. Create a new project with the InputSystem module
2. Change build platform to UWP
3. Change PlayerSettings->Configuration -> Scripting Runtime Version to ".NET 4.x Equivalent"
Expected:
No compile issues
Observed:
Numerous Ambiguous calls between System/System.Collections.Generic and UnityEngine.Experimental.Input.Net35Compatibility
Notes:
- Reproduced with 2018.2.0b11 and Trunk rev 96052d777ea1
- InputSystem\Utilities\Net35Compatibility.cs has include guards that look like they are meant to correct this. Perhaps these include guards have changed?
- Example Error: C:/Users/jackpr/AppData/Local/Unity/cache/packages/staging-packages.unity.com/com.unity.inputsystem@0.0.4-preview/InputSystem/Actions/InputActionManager.cs(465,42): error CS0104: IReadOnlyList' is an ambiguous reference betweenSystem.Collections.Generic.IReadOnlyList' and `UnityEngine.Experimental.Input.Net35Compatibility.IReadOnlyList'
douglas-piconi commented 28 days ago
@jackpr-unity Looks like this problem is outside of the input system code. Right now, the script compiler is broken and wrong for UWP in both the editor and the player. The pre compile defines that we use do not do anything. I'm messaging the scripting team and found a fogbugz bug that has already been filed by someone else, and will try to get this priority and user pain possibly bumped up.
https://fogbugz.unity3d.com/f/cases/1075345/
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment