Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0a1
2018.2.0f2
Issue ID
1062198
Regression
Yes
[Editor] Application.logMessageReceived being invoked when API calls are not allowed
To reproduce:
1. Download attached project "logMessageSafety.zip" and open in Unity
2. Open "scene" scene
3. Select "Repro" gameObject
4. In Inspector window reset "ConstructorBehaviour" script
Expected results: In Console will be printed two errors
Actual results: In Console will be printed two errors and Application.logMessageReceived will be invoked when API calls are not allowed
Notes:
- This issue reproduces on both Windows and OSX
- The error message itself is expected behavior, but Application.logMessageReceived is now being called as a result of the Log call in the Constructor
- A Customer is reporting this, but as a result of " Serialization depth limit 7 exceeded at..." message
Reproduced on Unity 2017.2.0a1, 2017.2.3p2, 2017.3.2f1, 2017.4.7f1, 2018.1.9f1, 2018.2.0f2 and 2018.3.0a5
Could not reproduce on Unity 2017.1.4p2
Regression on Unity 2017.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Screen position out of view frustum" error is shown when displaying populated World Space canvas in Multiplayer Play Mode secondary Editor using Input System UI Input Module
- Sprite width/height is rendered differently in the Game view than in the Scene view
- Debug Mode popup window is inaccessible/cut-off when opened on widescreen monitors or resizing to specific Editor Window resolution
- Post-processing Render Features using Render Graph do not work when URP 2D Renderer is used and Render Graph enabled
- [Unity Physics] The NativeList<DistanceHit> randomly returns fewer hits than expected when using CalculateDistance in Edit mode tests
Add comment