I created several scenarios with Katalon Recorder version 7.0.1, but after the 7.1.0 update, I cannot run any scenarios. Here are some errors found:
2 Likes
Hi there,
Thank you very much for your topic. Please note that it may take a little while before a member of our community or from Katalon team responds to you.
Thanks!
Hi @lucasdpl71,
Thank you for sharing your issue. Can you help provide the error logs?
kindly attach error logs or screenshots
I’m having the same issue in the last week or so, scripts that were previously working fine do not respond anymore, using Edge. (Refreshing the active browser tab does not work)
:
log:
[info] Playing test case Full Mature dependent / Full Mature Dependent
[info] Time: Wed Aug 21 2024 10:33:49 GMT+0100 (Irish Standard Time) Timestamp: 1724232829386
[info] OS: Windows Version: 10
[info] Browser: Edge Chromium Version: 127.0
[info] If the test cannot start, please refresh the active browser tab
Usually that error means that you’ve loaded the Chrome Extension after the page is already loaded. As such, the extension is unable to interact with the DOM (the web page) as the two are not configured to talk to each other.
It may sound like a dumb question, but have you tried to reloading the web page you’re using after seeing this error? As it might help to reload the page and then re-open the extension.
If this does not help, then it may be an Edge-specific issue?
1 Like
Same problem here but with Chrome Version 131. Tried clearing cache
1 Like
Hello !
Same thing here :
[info] Playing test case *********
[info] Time: Fri Jan 24 2025 11:48:47 GMT+0100 (heure normale d’Europe centrale) Timestamp: 1737715727894
[info] OS: Windows Version: 10
[info] Browser: Chrome Version: 132.0
[info] If the test cannot start, please refresh the active browser tab
[error] Error: Retry failed
Tried to refresh the page, empty cache, restart Chrome and KR, no effect.
It seems that it runs on Firefox. Has anyone a solution to easily migrate my tests from Chrome to Firefox ?
does it work on firefox or it doesn’t?
I’ve started running into the same issue since updaitng to the latest version of Chrome (on macOS). On version 133.0.6943.127. Prior to updating, had it working just fine.
Obviously, i’ve tried reloading the page, closing and re-opening the extension, restarting the browser, (even restarting the computer), disabled and reenabled the extension, etc. Also, i’ve tested with different scripts and changed the permissions around when the extension runs (to see if this had any impact).
The verbose logging has been particularly unhelpful in getting to the cause of this issue (even with collect errors enabled):
#### [info] Playing test case Product Tour Sample Test Suite / Book a healthcare appointment
#### [info] Time: Mon Feb 24 2025 16:50:06 GMT+0000 (Greenwich Mean Time) Timestamp: 1740415806232
#### [info] OS: macOS Version: 10.15.7
#### [info] Browser: Chrome Version: 133.0
#### [info] If the test cannot start, please refresh the active browser tab
#### [error] Error: Retry failed
#### [info] Pausing
#### [info] Stop executing
#### [info] Time: Mon Feb 24 2025 16:50:38 GMT+0000 (Greenwich Mean Time) Timestamp: 1740415838230
#### [info] Test case failed
By comparison, by inspecting the extension, the developer console allowed me to see its like a security / sandboxing issue:
(cc: @Elly_Tran @vu.tran)
1 Like
The following resource from Google explains the issue that appears to be happening here (and why) Manifest - Content Security Policy | Chrome Extensions | Chrome for Developers
Also, if it is handy, although I’ll presume the team already knows, this is a guide around ‘fixing’ CSPs: Csper: Content Security Policy made easy
There is also this evaluator tool available: Csper: Content Security Policy made easy
I encountered same problem as him and It seems logs cannot provide specific details
Hi all,
Our team is investigating and working on this. I will keep you guys updated on this soon
1 Like
Hi @guy.mason ,
I’m a developer at Katalon. I’ve tried to test the recorder again but still cannot reproduce your issue. So, can I have your testing site and the steps to reproduce the issue from my side?