Search Issue Tracker
Fixed
Fixed in 1.15.0
Votes
2
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment