Search Issue Tracker
Fixed in 1.4.1
Votes
0
Found in [Package]
1.3.0
Issue ID
1378614
Regression
No
[Input System] NullReferenceException error is thrown when using Input Actions in builds
How to reproduce:
1. Download the attached project "InputReader bug repro.zip"
2. Build and Run on a Standalone platform with Development build selected
3. Observe the logs
Expected result: No errors are printed in logs
Actual result: Logs show NullReferenceException error:
NullReferenceException while resolving binding 'Move:2DVector' in action map 'Controls (UnityEngine.InputSystem.InputActionAsset):Game'
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37)
Reproducible with: 1.0.0-preview (2019.4.34f1, 2020.3.26f1), 1.3.0 (2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b3, 2022.2.0a2)
Could not test with: 0.9.6-preview (2019.4.34f1, 2020.3.26f1) (compile errors)
Notes:
- Can be reproduced with Standalone and Android builds
- Can't be reproduced in Editor
- Not reproducible when deleting existing Up/Down/Left/Right Composite and creating a new one with the same parameters
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
- Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
Resolution Note (fix version 1.4.1):
Fixed in: Input System 1.4.1