Not signed in
Copyright © 2026 Unity Technologies
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.
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.
Steps to reproduce:
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:
Sign in to see your voted issues