Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.69f1
6000.3.10f1
6000.4.0b11
6000.5.0a8
Issue ID
UUM-135970
Regression
No
Removing Feature in Package Manager doesn’t remove its packages if they were already installed before installing the Feature
Reproduction steps:
1. Create a new project
2. Window > Package Management > Package Manager > Unity Registry
3. Install all packages of any of the Features separately (e.g. ProBuilder, FBX Exporter and Terrain Tools of 3D World Building Feature)
4. Install Feature that contains previously installed packages (e.g. 3D World Building Feature)
5. Click “Remove” button of newly installed Feature and observe the packages
Actual result: All packages included in the Feature remain installed after the Feature is removed
Expected result: All packages included in the Feature are uninstalled when the Feature is removed
Reproducible with: 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a8
Reproduced on: macOS Tahoe 26.3 (M4)
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.