Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.0.X
Votes
0
Found in
2023.1.0a20
2023.2.0a23
2023.3.0a3
6000.0.0b11
Issue ID
UUM-42439
Regression
No
Packman: "Remove" window shows assets with wrong icons
Steps to reproduce:
- Open or create a project
- Go to "Window" ->"Package Manager"
- Go to the "My Assets" section
- If you don't have any assets please download them (for example "Food pack - 3D Microgames Add-Ons")
- Click on a "+" on the import button
- Check that all the assets would be checked, and click the "Import"
- Verify, that assets were imported. Observe their icons.
- Go back to the "Package Manager" and find the same asset package
- Select the "Remove asset from project" option, which is displayed under the "In Project" button
- Verify, that the "Remove" window becomes visible and imported assets are displayed in it. Observe their icons.
Expected result: Assets should be displayed with the same icons.
Actual result: Assets are displayed with different icons. A screenshot is added in the Attachments section.
Reproducible with: 2023.1.0a20, 2023.1.4f1, 2023.2.0a23.
Not reproducible with: 2023.1.0a19, 2022.3.4f1, 2021.3.28f1 as "Remove" functionality doesn't exist in these streams.
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
- Polyspatial Material swap set animations are not firing when used in Play Mode and Players
- Incomplete shortcuts are displayed in the "Set" dropdown in Visual Effects Graph VFX Control subwindow
- Version change sub-window closes automatically when "Add Modules" subwindow is closed
- RenderTexture content from 'Depth Only' camera is not rendered correctly on UI RawImage when Multithreaded Rendering is enabled on specific MediaTek devices.
- Weight Brush Overlay text is clipped in Sprite Editor
Resolution Note:
We have verified that the issue reported has been resolved in the latest version of Unity, and as a result, we are unable to reproduce it.
Resolution Note (6000.0.X):
We have verified that the issue reported has been resolved in the latest version of Unity, and as a result, we are unable to reproduce it.