Search Issue Tracker
Fixed in 1.0.0-preview.1
Votes
0
Found in [Package]
0.1.2, 1.0.0
Issue ID
1189846
Regression
No
NullReferenceException errors are thrown when interacting with Input System Package Project Settings with QuickSearch installed
How to reproduce:
1. Create a new Unity project
2. Import the Input System package
3. Import the Quick Search package
4. Open Edit > Project Settings > Input System Package
5. Create settings asset
6. Add a new Supported Device(e.g. Mouse)
Expected result: no errors are thrown
Actual result: NullReferenceException errors are thrown
Reproducible with: 2019.1.0a10, 2019.1.14f1, 2019.2.0a2, 2019.2.8f1, 2019.3.0b6, 2020.1.0a8
Not reproducible with: 2018.4.11f1
Could not test with: 2017.4.33f1, 2019.1.0a9, 2019.2.0a1(Packages unavailable/Input System package incompatible)
Reproducible with Input System versions: 0.1.2, 1.0.0
Reproducible with Quick Search versions: 1.1.0, 1.4.1
Not reproducible with: Quick Search versions: 1.0.9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment