Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0a3
Issue ID
UUM-112551
Regression
No
The package creation workflow lacks clearer, more informative field validation messages
Steps to reproduce:
- Create a new Unity project
- Open Package Manager window
- Press “+” at the top left corner
- Select “Create package”
- Add a new package name and press “Create”
- Verify that the "Inspector" window displays the package manifest
- Click the "Edit" button in it
- From the "Name" field, delete the entered package title
- Observe the result
Actual results: User gets an error message "Invalid Package Name ''". The error message is inaccurate and uninformative because the "Name" field is empty.
Expected results:
- If the field is left empty (e.g., data is deleted completely), an error message should be displayed: "Name field is required. Please enter package name".
- If the user enters prohibited characters, a validation message should appear, indicating the issue and guiding the user on how to correct the input.
Reproducible with versions: 6000.3.0a3
Not reproducible with versions: -
Can’t test with versions: 6000.3.0a2 as "Create package" functionality landed only in 6000.3.0a3
Tested on (OS): M1 Max - Sequoia 15.5
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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.