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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
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.