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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.1):
Fixed in 2019.3.0f1, 2020.1