Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131805
Regression
No
Confusing validation message in Scoped Registries
Steps to reproduce:
- Create project
- Go to Edit > Project Settings
- Enter Scoped Registry Name
- Enter Scoped Registry URL
- Enter Scoped Registry Scope(s)
- Click "+" in a "Scope Registry" list to add a new one
- Enter the same Name but a different URL and "Scope(s)
- Click "Save"
- Observe the displayed validation message
Actual results: The first part of the validation appears to generate two separate messages (separated by a colon), while only a single explanation of the issue is shown.
Expected results: The validation should display one consistent error message, without splitting it into multiple parts, and provide a clear explanation of the issue.
Reproducible with versions: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Tested on (OS): macOS - Tahoe 26.2
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
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.
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.