Search Issue Tracker
By Design
By Design in 6000.3.X
Votes
0
Found in
6000.0.55f1
6000.1.15f1
6000.2.0f1
6000.3.0a4
Issue ID
UUM-113198
Regression
No
“Profile already exist” message appears in “Rename profile” window when trying to rename existing profile name
Steps to reproduce:
1. Create new Unity project
2. Open Shortcuts window (Unity > Shortcuts)
3. Open Profile list
4. Select to “Create new profile…”
5. Enter new Profile name, like “Test”
6. Press “Create”
7. Open Profile list again
8. Select “Rename profile…”
9. Observe the the message below the “Profile Name” field
Actual results: When opening “Rename profile” window user gets “Profile already exist” message without entering or reentering profile name
Expected results: “Profile already exists” message should appear if user enters the same name which already exists
Reproducible with versions: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Tested on (OS): macOS Silicon, Sequoia 15.5
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we are closing this issue.
This behavior is intended as the original name is the one set by default when "renaming" a profile. Then it's conflicting with an existing one (itself) and this is intended.
Thanks for the feedback on this, but after consideration we will keep the behavior of renaming this way.
Resolution Note (6000.3.X):
Thank you for bringing this issue to our attention. After careful consideration, we are closing this issue.
This behavior is intended as the original name is the one set by default when "renaming" a profile. Then it's conflicting with an existing one (itself) and this is intended.
Thanks for the feedback on this, but after consideration we will keep the behavior of renaming this way.