Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0b4
2019.3.0b9
Issue ID
1195747
Regression
Yes
Scripts are unable to compile after upgrading project to 2019.3.0b4
How to reproduce:
1. Open the user-supplied project
2. Observe the errors in the Console window
Expected result: after upgrading the project to Unity 2019.3.0b4, existing Scripts are still able to compile
Actual result: after upgrading the project in Unity 2019.3, Scripts are not able to compile and an error stating "Exception: No pending assemblies queued for compilation and no compilers running. Compilation will never finish." is thrown
Reproducible with: 2019.3.0b4, 2019.3.0b12
Not reproducible with: 2018.4.14f1, 2019.2.14f1, 2019.3.0b3, 2019.3.0f1, 2020.1.0a
Unable to test with: 2017.4.35f1
Note: unable to test on 2017.4.35f1 due to the Editor crashing on project launch.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.1):
Fixed in 2019.3.0f1, 2020.1