Thanks for letting us know
I guess rolling back the appium ver would not be the good solution
@ladestamaro.bonata rolling back to appium 1.22 hides the real problem, and you lose flutter. look at the path in your own log:
/Users/ladestamaro.bonata/node_modules/.cache/appium/extensions.yaml
appium keeps its driver list under APPIUM_HOME/node_modules/.cache/appium. by default APPIUM_HOME is ~/.appium, so that path means your terminal has APPIUM_HOME pointing at your home folder (or you installed the drivers from there with a local npm). katalon studio is launched from the dock, it does not see that env variable, so the appium it starts looks in ~/.appium, finds zero drivers and you get “could not find a driver for automationName UiAutomator2” even though appium driver list --installed in your terminal looks fine.
quick check: echo $APPIUM_HOME in the terminal where appium works. if it prints something, that is it.
fix is either of these:
- unset APPIUM_HOME, then
appium driver install uiautomator2andappium driver install flutteragain so they land in ~/.appium where the dock-launched katalon will find them, or - launch katalon from that same terminal (
open -a "Katalon Studio") so it inherits the variable.
then go back to appium 3.x. katalon 11 is built for appium 3 and docs say uiautomator2 7.x, and the flutter driver works there too.