Search Issue Tracker
Active
Under Consideration for 1.14.X
Votes
1
Found in [Package]
1.14.0
Issue ID
ISXB-1541
Regression
Yes
Null key present in Keyboard.current.allKeys when iterating through the key list
How to reproduce:
1. Open the “IN-99819_NullKeyboardKey“ project
2. Open the “SampleScene”
3. Enter Play Mode
4. Exit Play Mode
5. Observe the Console
Expected result: No keys are null
Actual result: A warning is present: “Null key detected at index: 110”
Reproducible with: 1.14.0(2022.3.61f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9)
Not reproducible with: 1.13.1(2022.3.61f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9)
Reproducible on: macOS 15.4.1 (M1 Max), Windows 11 (by user)
Not reproducible on: no other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment