Search Issue Tracker
Fixed
Votes
0
Found in
6000.3.0a3
Issue ID
UUM-112927
Regression
No
Uninformative and misleading validation during package creation
Steps to reproduce:
- Create a project
- Window -> Package Management -> Package Manager
- Click “+” and select “Create package”
- Enter "12345" into the package name and click “Create”
- Observe the newly created package name in the "Package Manager" window
Actual results: Instead of "12345," the user gets the "New Package" name
Expected results:
- Package Display Name should keep "12345"
- Package Technical Name should be renamed
- Warning should survive and be visible after domain reload
Reproducible with versions: 6000.3.0a3
Not reproducible with versions: -
Can’t test with versions: 6000.3.0a2 as package creation functionality landed just in 6000.3.0a3
Tested on (OS): M1 Max - Sequoia 15.5
Notes:
- A user gets a validation message in the "Install package by name" window. So the "Create package" window should have the same validation workflow. Users would be informed at that moment when they execute it, not a post action message in the "Concole" window when package with different title is created.
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
Fixed by another internal issue: UUM-113370: Data validation rules for Package Name are different between Package Creation and Edit views