Search Issue Tracker
Fixed in 2019.1.X
Assigning a custom Debug.logger.logHandler doesn't intercept thrown exceptions
1. Open project
2. Press play
Notice that the "Test" class intercepts Debug.Log and Debgu.LogException, but doesn't intercept the exception it throws.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
- The property of a component becomes read-only when it is bound to "PropertyStreamHandle"
- Physics.Raycast does not work when used on the whole model
- Shader Graph changes the Position of Prefab instances in Play mode
Jan 19, 2018 13:15
Present in 2017.1.2p3. It has almost 2 years. Duh!
May 02, 2017 09:26
Present in 5.4.5f1.
Is there any way to catch these?
May 24, 2016 16:54
Just ran into this issue. We're trying to route all exceptions to GetSentry.com, a REST service but are having significant trouble finding the correct point to insert logging hooks. Capturing all Debug.Log callbacks can be done through multiple means, but this appears to be the only place to get exceptions.
Except, while the LogFormat callback of the ILogHandler interface is called, the LogException callback is completely dormant.
This is still an issue as of 5.3.5f1