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
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
- ChangeSets are not detected when created via Editor Scripts
- "Cyclic Prefab nesting not supported" error window is thrown when trying to nest two sibling prefab variants
- BuildPipeline error is thrown when building Asset Bundles
- "IndexOutOfRangeException" errors appear when entering Play Mode if using "AsDeferredJobArray"
Resolution Note:
Fixed: In 2019.1 and above