Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0a3
Issue ID
UUM-112489
Regression
No
Details Information Container breaks in Package Manager if adding a long package description
Steps to reproduce:
1. Create new Unity project
2. Open Package Manager window
3. Press “+” at the top left corner
4. Select “Create Package”
5. Add new package name and press “Create”
6. Select newly created package
7. Press Manage > Edit Manifest
8. In Inspector > Brief description type “testing”
9. Copy text and paste as much as possible
10. Press “Apply”
11. Go back to Package Manager
12. Observe the Details Information Container
Actual results: Package details information container completely breaks, “Technical name” and “Minimum Editor Version” text disappear. Also ,not all the text is displayed and bottom margin dissapears.
Expected results: “Brief description” value field should have character limit which should not allow to add unlimited text in the description box
Reproducible with versions: 6000.3.0a3
Can’t test with versions: 6000.3.0a2 (Can’t create custom package)
Tested on (OS): macOS Silicon, Sequoia 15.5 (M1)
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.