Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
2019.3
2019.3.1f1
2020.1
Issue ID
1220989
Regression
No
Package version changes while Unity is running cause Play Mode compiler errors which go away after the Editor is restarted
How to reproduce:
1. Open the "RandomBugs.zip" project
2. Change the Packages/manifest.json with Packages/Repromanifest.json
3. In the project view, perform RMB > Refresh
4. Enter Play mode
5. Notice the errors in the Console
6. Exit Unity
7. Open the project again
8. Enter Play Mode
9. Notice that there are no errors in the Console
Actual result: Unity fails to successfully re-compile scripts for the first time and causes errors in the Console.
Expected result: Unity successfully re-compiles scripts in the first time.
Reproducible with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b11, 2020.2.0a13
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (fix version 1.3.0):
This is fixed in 1.3.0 but still requires a restart of the editor. There should be a popup dialog notifying that the editor should be restarted.