Search Issue Tracker
Fixed
Fixed in 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Not Reproducible in 6000.0.X
Votes
0
Found in
6000.0.65f1
6000.4.0b4
6000.5.0a5
Issue ID
UUM-132217
Regression
Yes
Legacy UI Elements are not entering auto renaming on creation
How to reproduce:
1. Create a new Unity project
2. In the Hierarchy, right-click -> UI (Canvas) -> Canvas
3. Observe the results
Expected results: The renaming is automatically entered on GameObject creation
Actual results: Renaming is not entered on GameObject creation
Reproducible with: 6000.4.0b2, 6000.4.0b4, 6000.5.0a5
Not reproducible with: 6000.0.65f1, 6000.3.31, 6000.4.0b1
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: Reproducible in both Hierarchy v1 and v2
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.4.0b7):
Fixed in 6000.4.0b7
Resolution Note (fix version 6000.3.7f1):
Fixed in 6000.3.7f1
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.