Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0a8
2020.1
2020.2
2020.2.0a11
Issue ID
1249190
Regression
Yes
UnityLinker fails to run when Assembly Definition Asset is named InputModule.dll
How to reproduce:
1. Open user's attached project
2. Make sure Scripting Backend property is set to IL2CPP in the Player Settings
3. Go to File -> Build Settings
4. Press Build
Expected result: Build is successful
Actual result: Build is stopped by an error from UnityLinker in the Console log
Reproducible with: 2019.3.0a8, 2019.3.15f1, 2020.1.0b10, 2020.2.0a13
Not reproducible with: 2018.4.23f1, 2019.3.0a7
Could not test with: 2017.4.40f1 (Managed code stripping not available)
Note: Build with Mono is also stopped if Managed Stripping Level property in Player Settings is not disabled.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2020.2):
Scripting: Fix engine code stripping bug when a user assembly was named InputModule.dll or matched any of the other engine module names.
Fixed in: 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.1f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.5f1