Search Issue Tracker
Fixed in 1.1.0-pre.5
Votes
1
Found in [Package]
1.1.0-preview.2
Issue ID
1305016
Regression
No
[InputSystem] Keyboard.current becomes Null after OnScreenButton is destroyed
How to reproduce:
1. Open the user's attached project ("InputSystemTest.zip")
2. Open the "Scene A" scene
3. Enter Play mode
4. In the Game View Click the On Virtual Pad button. Make sure to not touch the keyboard
5. Click the Off Virtual Pad button
6. A NullReferenceException occurs in TargetMovement.cs accessing Keyboard.current.
Expected results: Keyboard.current is only null when there is no keyboard
Acutal results: After OnScreenButton is destroyed that references a keyboard button, Keyboard.current becomes null
Reproducible with: Input system 0.9.0-preview, 1.1.0-preview.2 (2019.4.19f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a3)
Note: After clicking a button on the keyboard Keyboard.current is not null anymore
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
- Incorrect error box style when installing the unsigned package in the Package Manager's "Invalid Signature" pop-up
- "Invalid Signature" pop-up incorrectly wraps the text when using the Light theme
- WebGPU: can't bind compute RWTexture for read and write
- WebGPU: errors with unorm and half4 RWTexture
- Error indicating that Importer has not been disposed properly is logged when switching to or from the Texture Importer type in a Focused Inspector
Resolution Note (fix version 1.1.0-pre.5 ):
Fixed in: Input System 1.1.0-pre.5