Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.3.4f1

6000.4.0b4

6000.5.0a4

Issue ID

UUM-131971

Regression

No

Organization names with non-ASCII symbol characters are selectable in Inspector window, causing “Invalid Complete Package Name” error

Packman

-

Steps to reproduce:
1. Create a new Organization using emojis ([https://cloud.unity.com/account/my-organizations])
2. Create new Unity project
3. Open Package Manager window
4. Press “+” button
5. Select “Create package…”
6. Add any Package display name
7. Once created, select Manage > Edit Manifest
8. In Inspector window > Organization name select newly created Organization

Actual results: Field allows selecting Organization with unrecognizable symbols causing error “Invalid Complete Package Name “ “ thrown

Expected results: Only Organizations with recognizable symbols should be allowed to be selected, no errors thrown in the Console window

Reproducible with versions: 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Can’t test with versions: 6000.0.65f1 (feature not available)

Tested on (OS): Ubuntu 24.04, macOS Silicon Tahoe 26.2 (M1)

  1. Resolution Note:

    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.

  2. 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.