Search Issue Tracker
Fixed
Fixed in 2018.4.X
Votes
0
Found in
2018.4.13f1
2018.4.28f1
Issue ID
1289931
Regression
Yes
[Editor] Force quitting the editor mid build will leave code not compiling any more
Steps to reproduce:
1. Open the user's attached project "ErrorTest2018LTS.zip"
2. In the top menu select "Build/BuildAllAB or Build/BuildPlayer"
3. While the Editor is building force quit Unity through the task manager
4. Open the project
Expected results: The "Build" menu is in the same place
Actual results: The "Build" menu is gone
Reproducible with: 2018.4.13f1, 2018.4.29f1
Not Reproducible with: 2018.4.12f1
Fixed in: 2019.1.0a1
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note:
Fixed: In 2019.1 and above