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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment