*Summary
The console log shows all loggings (info, warn , error) in RED.
*Steps to reproduce
I installed Katalon v10.0.0 , changed appearance to theme “dark”.
*Expected Results
The colors of the logs should be respecting the settings and make distinction between warning, info and errors.
*Actual Results
All is in RED. It does not impact the Log Viewer view.
*Screenshots / Videos
Katalon preference console settings:
Blocker?
No
Hi @joost.degeyndt,
Sorry for my late response. I will deliver this issue to my team and take a look on this. Keep you updated soon!
Any resolution on this matter, I’m facing same issue. All the logs are in red therefore very hard to differentiate logs from actual ERRORS. (Katalon version 10.0.0)
Hi @joost.degeyndt and @mqamar,
We’ve acknowledged this issue and already planned to fix it in future releases. Thanks
For those interested (@mqamar ), fix is not yet available in v. 10.0.1.
Issue always present in 10.1.0 release.
Hi chị @Shin ơi,
It seems like this issue is still present in the latest update. Could you help to look into it?
Thanks chị,
Albert
The issue persists in the latest release (10.1.0).
Do you have an estimated timeline for the fix? It’s causing significant challenges during debugging and script execution.
I got the update from the team that some parts of the problem will be fixed by v10.1.1, released tomorrow. Hope this is clear to you. Thank you
I’m sorry, but nothing is fixed. I can still see logs in red, like warnings, and I am using 10.1.1. Are there any specific changes I need to make in settings?
Hello @Elly_Tran Is there any update on this issue as on version 10.1.1 still logs are appearing in red on console when we are executing any test step, compare to version 9 it is very difficult to read console tab in version 10 or above.
We hear you! Our team is actively working on this issue. We’ve addressed part of the logging problem in version 10.1.1, but the specific issue you’ve reported isn’t fully resolved yet.
Please bear with us, we’ll keep you updated once we’ve thoroughly fixed this in an upcoming release.
Thanks for your patience!
