Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.3
2020.3.4f1
2021.1
Issue ID
1351728
Regression
No
Unneccessary MonoBehaviours included because UnityRootStrategy command line parameter is ignored
How to reproduce:
1. Open the attached solution "UnityLinkerTests_.7z" in Visual Studio 2019
2. In "UnityLinkerTest.cs" edit "UnityInstallationPath" variable to Editor folder location
3. Run "TestUnityLinkStrategyCommandLineArgument" test
Expected result: test passes
Actual result: test fails
Reproducible with: 2020.3.15f2, 2021.1.16f1
Could not test with: 2019.4.29f1 (no dll), 2021.2.0b6, 2022.1.0a5 (Could not load file or assembly)
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a12
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b16
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.26f1