Search Issue Tracker
By Design
By Design 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
- Cinemachine camera does not jump to the target position when using CinemachineFollow.ForceCameraPosition
- Tree Prefab Asset icon does not display leaves
- Incorrect error box style when installing the unsigned package in the Package Manager's "Invalid Signature" pop-up
- "Invalid Signature" pop-up incorrectly wraps the text when using the Light theme
- WebGPU: can't bind compute RWTexture for read and write
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.