Search Issue Tracker
Fixed
Fixed in 1.15.0
Votes
0
Found in [Package]
1.14.1
Issue ID
ISXB-1636
Regression
No
"System.NullReferenceException: Object reference not set to an instance of an object" occurs when calling "FindKeyOnCurrentKeyboardLayout()" with arrow keys
How to reproduce:
1. Open the attached “IN-110290” project
2. Open the “SampleScene”
3. Enter Play Mode
4. Observe the Console window
Expected result: No errors appear in the Console window
Actual result: “System.NullReferenceException: Object reference not set to an instance of an object”
Reproducible with: 1.14.0 (2023.3.0a12), 1.14.1 (2023.3.0a12, 6000.0.55f1, 6000.2.0f1, 6000.3.0a4)
Could not test with: 1.9.0, 1.11.2, 1.12.0, 1.13.0, 1.13.1 (2023.3.0a12, 6000.0.18f1) (“Key not found on current keyboard layout.”)), 1.14.1 (2023.3.0a11 (Could not clear “error CS0117: 'BuildTarget' does not contain a definition for 'VisionOS'“))
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- There is also a warning stating “Null key at index 110 (Key.OEM5)”
- The issue only reproduces when using "upArrow", "leftArrow", etc, not when using "up" or "left"
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
taichis
Sep 04, 2025 06:33
In the WebGL version of Unity6000.0.56f1, the exception could not be caught by System.Exception, causing an alert to pop up and preventing the game from continuing.