Search Issue Tracker
Fixed
Fixed in 1.3.2
Votes
1
Found in [Package]
1.3.0
Issue ID
DSTR-692
Regression
Yes
Registered callbacks don't work after domain reload
Steps to reproduce:
- Unzip attached project
- Run tests from command line:
??Unity.exe -projectPath test-framework-callbacks -batchmode -testPlatform editmode -runTests??
If RunFinished callback was executed successfully, you should be able to find "RunFinished works" in the Editor.log. Notice that log entry is not in the Editor.log.
Extra steps:
- Disable CompilationPipeline.RequestScriptCompilation(); call in NewTestScript.cs (this will make it so that domain reload doesn't happen during test run)
- Run tests using command line again
- Inspect the Editor.log and notice that now you can find "RunFinished works" entry
Reproduced with: 2023.1.0a17
Reproduced with Test Framework 1.3.0
Not reproducible with Test Framework 1.1.33
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment