Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.1.6f1
Issue ID
1057320
Regression
No
OnTriggerExit2D() not triggered when collider gameObject is destroyed from another collider's OnTriggerEnter2D
To reproduce:
1. Download attached project "OnTriggerExit2DBug.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter Play mode
4. Observe that in Console there is no "OnTriggerExit2D()" printed after the ship is destroyed
Notes:
- This issue reproduces on both Windows and OSX
- Workaround: Set the Mine.ShowBug boolean to false and run the scene
- Destroying the collider gameObject from FixedUpdate() causes the expected OnTriggerExit2D()
Reproduced on Unity 2017.1.4p2, 2017.2.3p2, 2017.3.2f1, 2017.4.7f1, 2018.1.9f1, 2018.2.0f2 and 2018.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Add comment