Katalon mobile test issue

[ladestamaro.bonata]

Dear All,

i have this issue when i installed flutter driver, and when i want rollback this issue still not fixed

Caused by: org.openqa.selenium.SessionNotCreatedException: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Could not find a driver for automationName ‘UiAutomator2’ and platformName ‘android’. Have you installed a driver that supports those capabilities? Run ‘appium driver list --installed’ to see. (Lower-level error: Could not find installed driver to support given caps)

[nghi.phan]

Hi, the issue is not caused by Flutter rollback itself.
The main problem is that Appium cannot find the Android driver uiautomator2, which is required to start the session.

Please help check these items on your machine:

1. Run appium driver list --installed
2. If uiautomator2 is missing, run appium driver install uiautomator2
3. Restart Appium / Katalon and try again

If the issue still happens, please share:

• appium -v
• appium driver list --installed
• your Katalon Appium / Node.js configuration

Let me know if it works

Bella

[ladestamaro.bonata]

i already do this, and always stuck, i dont have any solusion

[ladestamaro.bonata]

are you have any specific version appium that work smoothly for mac m3?

[nghi.phan]

for Mac M3, the safer recommendation is:

• Node.js: 20 LTS
• Appium: 2.x (prefer a recent stable 2.x release, not Appium 1)
• Android driver: uiautomator2 latest compatible version
• Flutter driver: install separately only if needed

Suggested setup:

1. Install Node 20 LTS
2. Install Appium 2 globally
   npm install -g appium
3. Install Android driver
   appium driver install uiautomator2
4. If needed for Flutter
   appium driver install flutter

The reason for this is:

• Apple Silicon works better with newer Node/Appium combinations
• Appium 2 is the current supported model
• most session-start issues on M-series Macs come from missing drivers, Java/SDK path issues, or mixed Node/Appium environments — not from M3 itself

Hope this helps

[ladestamaro.bonata]

always issue even i add in desired capability, so i dont add it again

[ladestamaro.bonata]

appium -v
ID-L22100:~ ladestamaro.bonata$ appium -v

dbug Appium Parsed manifest file at /Users/ladestamaro.bonata/node_modules/.cache/appium/extensions.yaml: {

dbug Appium “drivers”: {

dbug Appium “xcuitest”: {

dbug Appium “automationName”: “XCUITest”,

dbug Appium “platformNames”: [

dbug Appium “iOS”,

dbug Appium “tvOS”

dbug Appium ],

dbug Appium “mainClass”: “XCUITestDriver”,

dbug Appium “scripts”: {

dbug Appium “build-wda”: “./scripts/build-wda.js”,

dbug Appium “open-wda”: “./scripts/open-wda.js”

dbug Appium },

dbug Appium “schema”: {

dbug Appium “$schema”: “http://json-schema.org/draft-07/schema”,

dbug Appium “type”: “object”,

dbug Appium “properties”: {

dbug Appium “webdriveragent-port”: {

dbug Appium “appiumCliDest”: “wdaLocalPort”,

dbug Appium “default”: 8100,

dbug Appium “description”: “Local port used for communication with WebDriverAgent”,

dbug Appium “maximum”: 65535,

dbug Appium “minimum”: 1,

dbug Appium “type”: “integer”

dbug Appium }

dbug Appium },

dbug Appium “additionalProperties”: false,

dbug Appium “title”: “XCUITest Driver Configuration”,

dbug Appium “description”: “Appium configuration schema for the XCUITest driver.”,

dbug Appium “$id”: “driver-xcuitest.json”

dbug Appium },

dbug Appium “doctor”: {

dbug Appium “checks”: [

dbug Appium “./build/lib/doctor/required-checks.js”,

dbug Appium “./build/lib/doctor/optional-checks.js”

dbug Appium ]

dbug Appium },

dbug Appium “pkgName”: “appium-xcuitest-driver”,

dbug Appium “version”: “7.35.1”,

dbug Appium “appiumVersion”: “^2.5.4”,

dbug Appium “installType”: “npm”,

dbug Appium “installSpec”: “appium-xcuitest-driver@7.35.1”,

dbug Appium “installPath”: “/Users/ladestamaro.bonata/node_modules/appium-xcuitest-driver”

dbug Appium },

dbug Appium “flutter”: {

dbug Appium “pkgName”: “appium-flutter-driver”,

dbug Appium “version”: “2.18.1”,

dbug Appium “installType”: “npm”,

dbug Appium “installSpec”: “appium-flutter-driver@2.18.1”,

dbug Appium “installPath”: “/Users/ladestamaro.bonata/node_modules/appium-flutter-driver”,

dbug Appium “appiumVersion”: “^2.4.1”,

dbug Appium “automationName”: “Flutter”,

dbug Appium “platformNames”: [

dbug Appium “iOS”,

dbug Appium “Android”

dbug Appium ],

dbug Appium “mainClass”: “FlutterDriver”,

dbug Appium “doctor”: {

dbug Appium “checks”: [

dbug Appium “./build/lib/doctor/checks.js”

dbug Appium ]

dbug Appium },

dbug Appium “scripts”: {

dbug Appium “download-wda-sim”: “./scripts/download-wda-sim.mjs”

dbug Appium }

dbug Appium },

dbug Appium “uiautomator2”: {

dbug Appium “pkgName”: “appium-uiautomator2-driver”,

dbug Appium “version”: “2.34.0”,

dbug Appium “installType”: “npm”,

dbug Appium “installSpec”: “uiautomator2@2.34.0”,

dbug Appium “installPath”: “/Users/ladestamaro.bonata/node_modules/appium-uiautomator2-driver”,

dbug Appium “appiumVersion”: “^2.0.0”,

dbug Appium “automationName”: “UiAutomator2”,

dbug Appium “platformNames”: [

dbug Appium “Android”

dbug Appium ],

dbug Appium “mainClass”: “AndroidUiautomator2Driver”,

dbug Appium “scripts”: {

dbug Appium “reset”: “scripts/reset.js”

dbug Appium }

dbug Appium }

dbug Appium },

dbug Appium “plugins”: {},

dbug Appium “schemaRev”: 4

dbug Appium }

dbug Appium Creating hash file directory: /Users/ladestamaro.bonata/node_modules/.cache/appium

WARN Appium Appium encountered 3 warnings while validating drivers found in manifest /Users/ladestamaro.bonata/node_modules/.cache/appium/extensions.yaml

WARN Appium Driver “xcuitest” has 1 potential problem:

WARN Appium - Driver “xcuitest” (package `appium-xcuitest-driver`) may be incompatible with the current version of Appium (v2.4.1) due to its peer dependency on older Appium v^2.5.4. Please upgrade `appium-xcuitest-driver` to vnull or newer.

2.4.1

• appium driver list --installed
  Listing installed drivers

  - xcuitest@7.35.1 [installed (npm)]

  - flutter@2.18.1 [installed (npm)]

  - uiautomator2@2.34.0 [installed (npm)]

  

[ladestamaro.bonata]

any solution? i’m still stuck on this issue

[nghi.phan]

I am currently checking with internal team. We will have you updated as soon as I have the information.

Bella

[dineshh]

There’s no single “Mac M3-only” Appium version, but there are best‑practice combinations that work reliably on ARM Macs (M1/M2/M3).

Recommended Setup for Mac M3

1. Use Appium 2.x (latest stable)

Appium 2.x is the current major version and is known to work well on ARM Macs. The recommended approach is:

• Install Appium 2.x (use latest or a specific recent 2.x version like 2.11.4, 2.12.1, etc.)

2. Install the UiAutomator2 driver explicitly

Your error says:

Could not find a driver for automationName ‘UiAutomator2’ and platformName ‘android’

This means the driver is missing, regardless of Appium version. You must install it:

# Install Appium 2.x globally
npm install -g appium

# Install the UiAutomator2 driver
appium driver install uiautomator2

Then verify:

appium driver list --installed

You should see uiautomator2 in the list.

3. Node.js version on M3

Use a recent Node.js (18.x or 20.x) from the official ARM installer:

brew install node
# or use the ARM .pkg from nodejs.org

4. Katalon Appium Configuration

In Katalon Studio, ensure your Appium capabilities include:

{
"automationName": "UiAutomator2",
"platformName": "android",
"appiumVersion": "latest" // or a specific 2.x version
}

If You Still Get the Error

The problem is not the Appium version itself, but the missing driver. Even the “best” Appium version won’t work if uiautomator2 is not installed.

Try this sequence:

1. Uninstall Appium:

   npm uninstall -g appium

2. Clean npm cache:

   npm cache clean --force

3. Reinstall Appium 2.x:

   npm install -g appium

4. Install UiAutomator2:

   appium driver install uiautomator2

5. Restart your terminal and Katalon, then run the test again.

If you share:

• appium -v

• appium driver list --installed

• Your Node.js version (node -v)

we can help you pick the 2.x version and configuration for your M3 setup.

[nghi.phan]

I have submitted a ticket to the Engineering team, we will let you know soon.

Bella

[ladestamaro.bonata]

@dineshh

4. appium driver install uiautomator2

still issue, and i already follow your step but didn’t work

node -v → v26.5.0

Listing installed drivers

- xcuitest@7.35.1 [installed (npm)]

- flutter@2.18.1 [installed (npm)]

- uiautomator2@2.34.0 [installed (npm)]

appium -v → 2.4.1

[nghi.phan]

Hi, thank you for sharing the details.
From the output, uiautomator2 is already installed, so the problem is likely no longer the missing driver itself.

At this point, the two most likely causes are:

1. Node v26.5.0 is too new / not a stable baseline for Appium 2.4.1
2. Katalon may be using a different Node/Appium environment from the one in Terminal

Could you please help check the following:

• screenshot of your Katalon Appium / Node.js configuration
• full Appium server log from the failed run
• output of which node
• output of which appium

Also, as a recommended stable setup on Mac M3, please try:

• Node.js 20 LTS
• Appium 2.x
• reinstall uiautomator2 after switching Node version

If possible, please switch from Node 26 to Node 20 LTS first, then restart Appium and Katalon and run again.strong text

Please let me know if this shed any lights.

[ladestamaro.bonata]

node -v

v20.20.2

[ladestamaro.bonata]

actually i already try this and still issue

[nghi.phan]

@ladestamaro.bonata

still issue, and i already follow your step but didn’t work

node -v → v26.5.0

Listing installed drivers

- xcuitest@7.35.1 [installed (npm)]

- flutter@2.18.1 [installed (npm)]

- uiautomator2@2.34.0 [installed (npm)]

appium -v → 2.4.1

Hi, thanks for sharing your current setup:

• Node.js v26.5.0
• Appium 2.4.1
• uiautomator2 installed
• flutter installed

Based on that, the issue is likely environment compatibility or Appium path mismatch, not a missing driver.

My recommendation is:

1. downgrade Node.js from v26.5.0 to Node 20 LTS
2. upgrade Appium from 2.4.1 to a newer stable Appium 2.x
3. reinstall uiautomator2 after the upgrade
4. restart Appium and Katalon, then test again

Reason:

• Node 26 is very new and may not be stable with this Appium setup
• Appium 2.4.1 is also quite old
• if Katalon uses a different Appium/Node path, the installed driver may still not be recognized during runtime

If it still fails after that, please share:

• screenshot of Katalon Appium / Node.js configuration
• output of which node
• output of which appium
• full Appium server log from the failed run

That will help us confirm whether this is a version issue or a path mismatch.

[arvind.choudhary]

@ladestamaro.bonata

WARN Appium - Driver “xcuitest” (package `appium-xcuitest-driver`) may be incompatible with the current version of Appium (v2.4.1) due to its peer dependency on older Appium v^2.5.4. Please upgrade `appium-xcuitest-driver` to vnull or newer.

Above warning clearly tells : Your Appium server (core) is still on v2.4.1, but the drivers you have installed (xcuitest 7.35.1, uiautomator2 2.34.0) expect a much newer core. So, So even though appium driver list --installed correctly shows uiautomator2@2.34.0 [installed (npm)], the outdated Appium core (2.4.1) can’t properly read/register that driver’s manifest entry.

So, reinstalling uiautomator2" alone will not fix your problem. and which is not working as well

[arvind.choudhary]

Please try the below fix

1. Upgrade Appium Core (not just the driver)

Make sure the Appium server itself is running version 2.5.4 or later:

npm install -g appium@latest

appium -v

Verify that the reported version is 2.5.4 or higher.

2. Reinstall the Driver

After upgrading Appium, reinstall the UiAutomator2 driver to rebuild the driver manifest cleanly:

appium driver uninstall uiautomator2

appium driver install uiautomator2

appium driver list --installed

Confirm that uiautomator2 appears in the list of installed drivers.

3. Verify APPIUM_HOME Consistency Between Terminal and Katalon

This is one of the most common causes on macOS, especially on Apple Silicon (M-series) machines.

If Katalon Studio is launched from Finder/Dock instead of a terminal, it may not inherit the same environment variables (PATH, APPIUM_HOME, or the nvm-selected Node version). As a result, Katalon might be using a different Appium installation than the one where the drivers were installed.

Run the following commands in the terminal where Appium works correctly

echo $APPIUM_HOME

which appium

which node

Then verify in Katalon Studio > Project Settings > Execution (or wherever your local Appium configuration is defined) that Katalon is using the same Appium binary and Node.js installation.

If you’re unsure, launch Katalon directly from that terminal session so it inherits the same environment:

open -a "Katalon Studio"

4. Ensure the Same Node.js Version Is Used

On Mac M3 systems, Node.js 20 LTS is generally the safest baseline for Appium 2.x. However, what matters most is that:

• Appium was installed using that Node version.
• The Appium drivers were installed using that Node version.
• Katalon is launching Appium using that same Node version.

A mismatch between any of these can lead to driver detection issues.

5. Validate and Retest

Once Appium Core, drivers, and environment variables are aligned, run:

appium driver list --installed

Verify that the driver is still present, then rerun your Katalon mobile test.

If the issue persists, if possible share the outputs of:

appium -v

appium driver list --installed

echo $APPIUM_HOME

which appium

which node

These details will help identify whether the problem is related to Appium Core, driver registration, or an environment/path mismatch.