Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.11f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Votes
0
Found in
2021.3.29f1
2022.3.7f1
2023.1.9f1
2023.2.0b8
2023.3.0a4
Issue ID
UUM-48040
Regression
No
Misleading error shown when typing too many characters in Shortcut Profiles names
How to reproduce:
1. Open any project
2. Navigate to Edit > Shortcuts
3. Select a Profile
4. Select the same Dropdown Menu when selecting a profile and select "Rename Profile"
5. Start typing lots of characters
6. Observe Error/Warning
Actual result: Warning "Name contains unsupported characters"
Expected result: "Name contains too many characters" etc. as the previous warning indicates the issue is unsupported characters and not too many characters
Reproducible with: 2021.3.29f1, 2022.3.7f1, 2023.1.9f1, 2023.2.0b8, 2023.3.0a4
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a8):
Thank you for reporting this issue. The error message has been reformulated in the latest version Unity.
Resolution Note (fix version 2023.2.0b12):
Thank you for reporting this issue. The error message has been fixed.
Resolution Note (fix version 2023.1.16f1):
Thank you for reporting this issue. The error message has been fixed.
Resolution Note (fix version 2022.3.11f1):
Thank you for reporting this issue. The error message has been fixed.
Resolution Note (fix version 2021.3.31f1):
Thank you for reporting this issue. The error message has been reformulated.