Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.2.0a1
2018.3.0a1
2019.1.0a1
2019.1.0a12
Issue ID
1106450
Regression
Yes
"EditorUtility.scriptCompilationFailed" not flagging Package compilation errors during Editor startup
Reproduction steps:
1. Open "Samples.zip" project
2. Re-Open project
3. Run Editor Tests
Expected Result: Editor Tests don't run, because of compilation errors
Actual Result: Editor Tests run, despite there being compilation errors
Fixed in: 2019.2.0a7
Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2018.2.20f1, 2018.1.9f2
Did not reproduce on: 2017.4.19f1
Note:
Reproduces if opened twice in one Major Release Cycle (e.g. 2019.1.0a14 to 2019.1.0a1 reproduces)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warning icon is cut off and misplaced in Inspector when selecting a Shader with a compiler warning
- AI Navigation Sample Scenes do not work and throws “InvalidOperationException”, “Curl error3”, “CrashReporter”, and “NullReferenceException” errors when using the new Input System Package (default) on a new project
- Bottom of Build Size window in Project Auditor becomes inaccessible when a monitor has a high display scaling
- AI Assistant fails to load account information when AI assistant is opened
- [Linux] Improve "GPUResidentDrawer" warning message to include actionable guidance when creating a new Unity project using Universal 3D Template
Add comment