Please find my solution at
I will no longer use the “Tools > Upgrade WebDrivers > Chrome” as it frequently breaks.
Please find my solution at
I will no longer use the “Tools > Upgrade WebDrivers > Chrome” as it frequently breaks.
Hi,
I also agree with you on this urgency. I have let my team know and we already acknowledged this issue. We expect to hot-fix this problem and release it on v9.3.1 at the end of this February. If there are any changes, I will let you know soon.
Reference for other threads:
If anyone knows relevant threads, please link them to this thread. Hope this can help you and others updated. Thank you!
In addition of that, this is not the first case for such.
Feel free to search the forum, were reported also cases when Firefox updates stopped to work due to a ‘misterious’ mechanism using some ‘questionable tags’ hosted on Katalon repos.
And chrome-driver issues seems to be more and more periodic.
katalon simply do not keep-up with upstream changes … all the time the solution is “workarounds”
I would notify a thing to those who are currently using the Katalon Studio Free Plan of the older versions prior to v9.1.0.
When you upgrade your Katalon Studio to v9.3.1 to workaround the ChromeDriver issue, then your “custom keywords” would stop to function. As of v9.1.0 and newer. the “Custom Keyword” is an enterprise feature that requires payment. If you want to the fix of the ChromeDriver issue in v9.3.1 and continue to use custom keywords, you will be charged.
I suspect that Katalon is going to change the URL of the latest ChromeDriver, which is hard coded in the program of “Tools > Update WebDrivers > Chrome”. Then I am afraid that similar insident will reccur in future after v9.3.1 when the ChromeDriver project changes the format of the URL again.
Their official announcement instructs users to use the following command to get the latest version:
# Download the latest available ChromeDriver version corresponding to the Canary channel.
npx @puppeteer/browsers install chromedriver@canary
Please note that this command is tolerant for any possible changes in the format of download URL. They have no reason to hesitate chainging the format in future. How careful they are!
I would suggest that Katalon Studio must do the same processing: need to dynamically resolve the URL; Katalon Studio should not have any hard code for the URL format at all.
I’m getting the same issue. Katalon is downloading 114 instead of latest version using “Tools > Update WebDriver > Chrome” now all my tests are not working ![]()
This is unacceptable. I start regression today and now ALL chrome testing will need to be done manually. This is not the first time we have been dead in the water with Chrome and Katalon. Katalon is a testing tool and needs to work consistently, otherwise why are we paying a premium to use it? Now I have to explain to my management why we cannot use Katalon for regression…again. Need new ideas on how to make Chrome for Testing usable and upgradeable at will, in the application so that we are not impaired by a random Chrome update.
Hi @kazurayam,
Thank you for your suggestion. I will loop @xuan.tran here to consider your feedback and apply it to our implementation.
Hi @frank.page,
Sorry to hear that you face this trouble with lots of effects like that. We understand the huge impact of this issue and would like to fix it asap. Hope you can understand our attempt.
Thank you!
My suggestion:
$ npx @puppeteer/browsers install chrome@116.0.5793.0
and
$ npx @puppeteer/browsers install chromedriver@116.0.5793.0
as the official blog instructs.
2. Katalon Studio should add “Chrome for Testing” as a new type of browser to choose, as this:
3. Katalon Studio should provide a new setup where each users specify the path of the binaries of “Chrome for Testing” and the associated ChromeDriver.
4. Katalon Runtime Engine should provide a new commandline option to specify the paths of the binaries as well.
5. The Docker container should provide certain version of Chrome for Testing and ChromeDriver preset.
This support article has the two workarounds that can be used for the chrome v121 issue:
https://katalon-inc.my.site.com/katalonhelpcenter/s/article/Issue-Unable-to-upgrade-Chromedriver121
Perfect, I agree with that, it would work for me and I would assume many others who use the product every day.
Hello,
Both the work arounds mentioned in https://katalon-inc.my.site.com/katalonhelpcenter/s/article/Issue-Unable-to-upgrade-Chromedriver121 is not working for me. I am still facing the same error.
Is this something Katalon consider it as an outage or a minor inconvenient?
I will gladely like to know the opinion on this matter from:
@vu.tran
@mverinder
@support.squad
… grabbing popcorn …
Me too, I cannot use the Katalon with those workarounds. And our auto tests have been stopped for several days, which means our releases will be hampered
https://katalon-inc.my.site.com/katalonhelpcenter/s/article/Issue-Unable-to-upgrade-Chromedriver121
writes
/Applications/<Katalon Studio.app>/Contents/Eclipse/configuration/resources/tools/webdriver/webdrivermanager-5.4.1-fat.jar
I think this path applies to Mac only. Not applicable to Windows, Linux.
Same for me and in the middle of regression, so no time to do a lot of reconfiguration. I can use Edge, but most of our users use Chrome.
Up until now, 3 persons have raised their hands.
Only 3? Such small number, I am impressed.
I doubt if 3 is the actual size of active users who use Katalon with Chrome. Others are not yet aware of the incident, perhaps.
More will come, no worries.
As you already noticed, there are already similar topics raised here and there …
I am interested to see how many (or how few) really active members there are in the 60,000 community members.
i suppose the remaining 59997 are just ‘paid’ users so they just ‘submit servicedesk tickets’ …