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
- Material's icon doesn't fit the "Material preview not available" text when the Material doesn't have a preview
- Two fields in GLTF Importer Inspector are misaligned with other settings
- Duplicate image components can be added in m_TrackedTextureLess images and are never removed
- Cancelling a Package installation leads to invisible compilation errors preventing the user to enter Play Mode when the “Cancel” button is clicked, and does not actually cancel the package install as it appears in the Project after the Editor is restarted
- NullReferenceException occurs when searching presets in “Select Preset” window after selecting a GLTF Importer preset
Add comment