Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1316165
Regression
No
UnityLinker doesn't abort the Build if the assembly reference is missing
How to reproduce:
1. Create a new Unity project
2. Import the "link.xml" file and put it in the Assets folder
3. Build and Run the project
Expected results: The project should fail to build
Actual results: The project builds successfully
Reproducible with: 2019.4.23f1, 2020.3.1f1, 2021.1.0f1, 2021.2.0a10
Could not test with: 2018.4.33f1 (Building the project gives unrelated errors and fails the Build)
Note:
-Reproduces both with Mono and IL2CPP backends
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
- HDR Output gets disabled in the Editor when Reflection Probe is enabled during runtime
- The "Build and Run" Menu option tries to build for the selected Build Platform instead of the Active Build Platform
- Font kerning breaks at runtime when multiple UI Documents use different fonts
- MissingReferenceException occurs when entering Play mode with a locked GameObject in the Inspector
- Return value and out parameter get scrambled when a Custom HLSL Operator is used
Resolution Note (2021.2.X):
The UnityLinker will not error when an assembly mentioned in a link.xml file does not exist. Although providing an error might be desired behavior, there are many projects with link.xml files (either hand-written or generated by some other code) that depend on the current non-error behavior. We don't feel like causing these projects to fail to build is the proper behavior.