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
- Bunch of "TargetParameterCountException" errors thrown in the Editor Console when opening the "Adaptive Probe Volumes" tab in the "Lighting" window
- Non-removable serialized data for a renderer feature still appears even when the renderer feature is deleted
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
Add comment