Search Issue Tracker
Active
Under Consideration for 1.14.X
Votes
1
Found in [Package]
1.14.1
Issue ID
ISXB-1620
Regression
No
InputTestFixture.TearDown() fails to reset Input System state between consecutive scene-based tests
Reproduction steps:
1. Open the attached “IN-107889.zip” project
2. Open the “Playground” Scene
3. Open the Test Runner Window (Window > General > Test Runner)
4. Click on the Playmode tab
5. Click “Run All”
6. Observe the test results
Expected result: Both tests run successfully
Actual result: “TestOneSuccess” test runs successfully, and “TestOneSuccessAgain” (same test as first) test fails
Reproducible with: 1.9.0, 1.14.1 (6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a3)
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- Tests do not fail when run one by one, but Input actions become null in subsequent tests
- Removing InputTestFixture.TearDown() makes consecutive tests pass
- Issue persists even with DestroyImmediate() instead of Destroy()
- Cleaning all GameObjects in the Scene also does not help
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