Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0a11
2023.3.0a1
Issue ID
UUM-43958
Regression
No
Shortcuts: A user gets "Profile already exists" validation during the default profile rename workflow
Steps to reproduce:
- Create a project
- Go to the menu "Unity" -> "Shortcuts"
- Verify, that the "Shortcuts" window opens
- In the profile drop-down menu select "Create New Profile"
- Leave the default proposed name and save it
- In the profile drop-down menu select "Rename Profile"
- Observe the window
Expected result: Latest profile name should be displayed. No validation messages should be.
Actual Result: A user gets a validation message that such profile name already exists. Added screenshot in the "Attachments" section.
Reproducible with: 2023.2.0a11, 2023.2.0b2, 2023.1.6f1, 2022.3.6f1, 2021.3.29f1
Not reproducible with: 2023.2.0a10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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 (2023.3.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.