Search Issue Tracker
Fixed in 2019.2
Fixed in 2018.3, 2019.1
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
- Crash on SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
- Shader effect with specific view disappears when multiple materials in scene are present
- Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Add comment