Search Issue Tracker
By Design
Votes
0
Found in
2022.3.55f1
6000.0.32f1
6000.1.0b2
Issue ID
UUM-92560
Regression
No
Packman: The same asset data is displayed differently in "Import" and "Remove" popups
Steps to reproduce:
- Open or create a project
- Go to "Window" ->"Package Management" -> "Package Manager"
- Go to the "My Assets" section
- If you don't have any assets please download them (for example "Sunny Land")
- Import it. In the "Import" popup observe the top section. It displays an image and title "Sunny Land"
- 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
- Observe the "Remove" window
Actual results: Instead of the asset image, we see the Unity logo and instead of "Sunny Land" we see "Sunny Land 1.1". Screenshots are added in the "Attachment" section.
Expected results: The same image and the same title should be displayed. If the version has to be, it should be displayed in both popups. If the version number is not needed, so it should be removed and from the "Remove" window UI.
Reproducible with versions: 6000.1.0b1, 6000.0.32f1, 2022.3.55f1.
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): Apple M1 Max
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
The image of the package lives inside the .unitypackage. When we invoke remove, we do not try to read from the .unitypackage but instead read from the asset origin of all the files in the project, so we do not have access to the image.