Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
19
Found in
2020.1.0a24
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1309540
Regression
Yes
Application.quitting event is not raised when closing build
Reproduction steps:
1. Open the user's attached project
2. Build the SampleScene scene
3. Launch the build
4. Close the build and check the Player.log
Expected result: "Quitting the Player" is logged in the Player.log
Actual result: "Quitting the Player" is not logged in the Player.log
Reproducible with: 2020.1.0a24, 2020.1.17f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a3
Not reproducible with: 2019.4.19f1, 2020.1.0a23
Notes:
1. With 2020.1.11f1 - 2020.2.3f1 event is not raised and there is a delay when closing the build (Mono Scripting backend)
2. With 2021.1.0a1 - 2021.2.0a3 event is not raised but there is no delay when closing the build (Mono Scripting backend)
3. With 2020.1.0a24 - 2021.2.0a3 event is not raised but there is no delay when closing the build (IL2CPP Scripting backend)
4. Reproducible with Windows and Mac builds
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
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a8
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b12
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.0f1