Search Issue Tracker

Fixed

Fixed in 6000.6.0a2

Won't Fix in 6000.5.X

Votes

0

Found in

6000.3.3f1

6000.4.0b3

6000.5.0a4

6000.6.0a1

Issue ID

UUM-131291

Regression

No

"Create Package..." display name in Package Manager does not show correctly when the character limit is reached

Packman

-

Steps to reproduce:

  1. Create a new Unity project using a 3D Universal Template
  2. Open the Package Manager
  3. Click the "+" icon
  4. Select "Create Package..."
  5. Enter around ~120 characters
  6. Observe that no error/warning is shown
  7. Click Create
  8. In the Package Manager, select the created package
  9. Click Manage > Edit Manifest
  10. Select the package asset
  11. In the Inspector, add an additional character to the "Name" value
  12. Observe the bottom of the Inspector

Actual results: At the bottom of Inspector a "Invalid Package Name" error is shown, and no changes can be applied to the manifest without deleting characters

Expected results: The allowed character limit should be clearer, because the Package Manager allows a higher value, while the Inspector later on shows an error 

Reproducible with versions: 6000.3.3f1, 6000.4.0b3, 6000.5.0a4

Can’t test with versions: 6000.0.64f1 (no "Create Package..." option)

Tested on (OS): Windows 11

Notes:

  • If around 200 characters are entered in the 5th step, the warning is shown and the package cannot be created, but the warning should be shown with 120 characters as well or handled better, because later on, adding even one character showcases the "Invalid Package Name" error. And while the error is shown, a new package with the same name can still be created through Package Manager
  1. Resolution Note:

    Fixed in 6000.6.0a2

  2. Resolution Note (fix version 6000.6.0a2):

    Fixed in 6000.6.0a2

  3. Resolution Note (6000.5.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.