Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.1.0a4
Issue ID
682198
Regression
No
Application.logMessageReceived: assignment deactivates on-screen errors in standalone
To reproduce:
1. Open reproScene.unity
2. Select File/Build & Run
3. Observe that no errors print on-screen in the standalone build
4. Close the standalone player build
5. Comment out the line "Application.logMessageReceived += HandleUnityLogMessage;" in LogErrorBugReproComponent.cs and save the file
6. Build & Run
7. Observe that the error prints onscreen in the standalone player build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
Add comment