Search Issue Tracker
Fixed in 2018.4.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.8f1
Issue ID
1188715
Regression
No
Unity test running in batch mode fails when adding new assemblies
How to reproduce:
1. Extract the "repro.zip" folder
2. Change path variables according to your machine in "repro.sh" script
3. Execute the "repro.sh" script
Actual result: Unity loses reference to Assembly2.dll and tests fails with compilation errors.
Expected result: Unity keeps the reference and tests are executed.
Reproducible with: 2017.4.33f1, 2018.4.11f1, 2019.1.0a1.
Not reproducible with: 2019.1.0a2, 2019.1.14f1, 2019.2.8f1, 2019.3.0b6, 2020.1.0a8.
Notes:
- With 2017.4.33f1, on the first run the assembly is still missing but the tests are executed.
---------------------------
Fixed in 2019.1.0a2, 2018.4.13f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Selected Korean input text in UIToolkit TextField is not fully replaced when refocusing and entering new input
- [UITK Controls] Non text InputField can't be reset by API
- Control Scheme name field has no character limit, causing “Add Control Scheme” window to expand if name is too long
- Prefab variants do not keep the values of linear drag and angular drag while upgrading the project from Unity 6000.0
- UI Toolkit Debugger Pick Element does not react to the Burst Inspector window when hovering over the Burst Inspector window
Add comment