Search Issue Tracker
Fixed in 2017.3.X
Votes
0
Found in
5.5.3f1
Issue ID
912719
Regression
No
[Android] Debug.LogException is filtered as "I" Information instead of "E" error in logcat logs
To reproduce:
1. Download and open "rotate-test.zip" project.
2. Build application on a device.
3. Run logcat and filter information which Unity outputs.
4. Run the application.
5. Notice in logcat's outputted information that Debug.LogException is shown as "I" (Information).
Expected result: Debug.LogException is shown as "E" (Error).
Actual result: Debug.LogException is shown as "I" (Information).
Reproduced with : 2017.1.0b6, 5.6.1p1, 5.5.3p2, 5.4.5p1
Devices under testing:
Samsung SM G925F (Galaxy S6 Edge), OS:6.0.1, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zeroltexx/zerolte:6.0.1/MMB29K/G925FXXU5DQA7:user/release-keys
Samsung SM G928F, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zenltexx/zenlte:6.0.1/MMB29K/G928FXXS3BPIA:user/release-keys
Samsung SM G928F, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zenltexx/zenlte:6.0.1/MMB29K/G928FXXS3BPIA:user/release-keys
Notes: Neither iOS or standalone build logs shows the level of LogException. Everything is as expected when exception is thrown in the editor(it is thrown as an error).
Verified with 2017.3.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment