Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0b2
Issue ID
UUM-117775
Regression
No
Length validation for package name lacks clarity and timeliness
How to reproduce:
1. Create a project
2. Window -> Package Management -> Package Manager
3. Click “+” and select “Create package”
4. Enter this string "LoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsumLoremIpsum" into name and click the “Create”
5. Observe the result
Expected results: When the user enters the maximum allowed number of characters in the package name, the "Create" button becomes disabled, and an informative error message is displayed indicating that the character limit has been exceeded and needs to be corrected
Actual results: The "Create" button remains active and clickable even after the user exceeds the maximum character limit. The validation message only appears after clicking the button, and the message is not sufficiently clear
Reproducible with: 6000.3.0a3, 6000.3.0b2
Can't test with: 6000.3.0a2 as this build has no package creation feature
Tested on (OS): M1 Max - Sequoia 15.6.1
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
We have confirmed the issue. However, the fix for it will not be prioritized in the near future, so we're closing this ticket. We might reopen this ticket if priorities change.