Search Issue Tracker
By Design
Votes
0
Found in
6000.3.0a4
Issue ID
UUM-113748
Regression
No
[Usability] Clicking "Customize" on a Unity package is not revertable when no changes were made
How to reproduce:
1. Create a new Unity project
2. Open the Package Manager (Window -> Package Management -> Package Manager)
3. Select any Unity package which is not a dependency
4. Click Manage -> Customize
5. Observe the results
Expected results: The package is "Custom" but you can convert it to the default Unity version
Actual results: The package becomes "Custom" and it's impossible to convert it back to the default version
Reproducible with: 6000.3.0a4
Can't test with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1 (no such functionality)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Note: It would be nice to have a functionality that could revert this without the need to reinstall the package
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:
To revert a customized Unity registry package, simply hit _Manage > Remove_ and it will revert to the Unity registry package version.