Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2020.1.0a11
Issue ID
1194757
Regression
No
[VCS] Reverting the manifest.json file does not lock the Editor until the packages are fully reverted
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce
3. Submit the initial project and open the package manager
4. Install the Universal Render Pipeline package
5. Revert the package manifest.json file and immediately try to create the URP specific Pipeline Asset in the Project Window (Right-click -> Create -> Rendering -> Universal Render Pipeline -> Pipeline Asset)
6. Observe that it loses its filename, icon and a null reference exception is thrown in the console
Expected result: reverting the package manifest.json file locks the Editor until all of the packages are fully reverted preventing issues with packages that are being uninstalled (Same way the Package Manager already does it)
Actual result: reverting the package manifest.json file does not lock the Editor. This can cause issues with "half uninstalled" packages like the one described in the reproduction steps.
Reproduced in: 2020.1.0a11, 2019.3.0b9, 2019.2.10f1, 2018.4.12f1
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][Mobile Notifications] The Player freezes or crashes when calling "AndroidNotificationCenter.GetNotificationChannel" every frame
- Tile Palette selected dropdown text does not update when palette is renamed
- ArgumentException thrown and reference to Template gets unset when opening UXML file after editing referenced Template in Play mode
- [iOS][WebGL] Player freezes when multiple properties of a VisualElement are changed at the same time
- Warning 'GetControlID at event ValidateCommand returns a controlID different from the one in the Layout event' is logged when undoing the deletion of an Edited Freeform 2D Light
Resolution Note:
This is a real issue, but seems very low prevalence issue with a clear workaround of just waiting after performing this action.