Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
2.1.1
Issue ID
1126189
Regression
Yes
Multiple restarts needed when upgrading and installing packages in 2019.1
When upgrading a project from 2018.3.5f1 to 2019.1.0b2 Unity needs to be restarted a number of times before packages are updated correctly.
Steps to reproduce
- Clone the project here (git@github.cds.internal.unity3d.com:unity/Internal-UnityNeonDemo.git)
- Open in Unity 2019.1.0b3
- Head to the Window dropdown menu
- Notice issue - Package Manager is no longer available.
- Restart Unity - Pakage manager is now available.
- Notice Cinemachine and Timeline issues in the console.
- Open Package manager and update Cinemachine
- Notice that issues still remain in the console
- Restart Unity - Cinemachine and timeline issues are gone.
Expected
Unity should not need a restart when upgrading or installing updated packages.
Tested: 2019.1.0b3,2019.1.0b2
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #1068891