Unable to create a new remote session - Could not find a driver for automationName 'uiautomator2' and platformName 'android'

Hello. I’m attempting to record a mobile automation on an emulator, pretty much just following the tutorial.
I have the following installed:

  • Appium 2.5.1
  • Node.js v21.1.0 / npm 10.2.0
  • .NET SDK 9.0.100-preview.1.24101.2
  • java version “17.0.9” 2023-10-17 LTS
  • Android Studio (for the emulator)

And then I’m hit with this error from Katalon. Anyone can provide a solution? Thanks.

2 Likes

Try installing the uiAutomator2 driver for Android.
using the command - > appium driver install uiautomator2

if you face the same after installing it
pls share the capability you are using and the appium version here.

3 Likes

Thanks a lot, that worked. You’ve just saved a guy’s job application.

1 Like

please mark it as a solution for future reference

I have installed it but it still doesn’t work?
image

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!

Can you please share your log to triage the root cause

=============== ROOT CAUSE =====================

Caused by: org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: 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)

For trouble shooting, please visit: https://docs.katalon.com/katalon-studio/docs/troubleshooting.html

================================================

02-19-2025 04:33:11 PM Test Cases/Verify Correct Alarm Message

Elapsed time: 9.401s

Test Cases/Verify Correct Alarm Message FAILED.

Reason:

com.kms.katalon.core.exception.StepFailedException: Unable to start application: ‘E:\OneDrive - Apsis Solutions Ltd\Automation Projects\Katalon\PRISM_App_Katalon\androidapp\APIDemos.apk’

at com.kms.katalon.core.mobile.keyword.internal.MobileKeywordMain.stepFailed(MobileKeywordMain.groovy:64)

at com.kms.katalon.core.mobile.keyword.internal.MobileKeywordMain.runKeyword(MobileKeywordMain.groovy:34)

at com.kms.katalon.core.mobile.keyword.builtin.StartApplicationKeyword.startApplication(StartApplicationKeyword.groovy:91)

at com.kms.katalon.core.mobile.keyword.builtin.StartApplicationKeyword.execute(StartApplicationKeyword.groovy:48)

at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:74)

at com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords.startApplication(MobileBuiltInKeywords.groovy:49)

at Verify Correct Alarm Message.run(Verify Correct Alarm Message:16)

at com.kms.katalon.core.main.ScriptEngine.run(ScriptEngine.java:194)

at com.kms.katalon.core.main.ScriptEngine.runScriptAsRawText(ScriptEngine.java:119)

at com.kms.katalon.core.main.TestCaseExecutor.runScript(TestCaseExecutor.java:448)

at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:439)

at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:418)

at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:410)

at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:285)

at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:137)

at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:125)

at TempTestCase1739961187052.run(TempTestCase1739961187052.groovy:25)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Caused by: org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: 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)

Host info: host: ‘SE_SQA’, ip: ‘’

Build info: version: ‘4.22.0’, revision: ‘c5f3146703’

System info: os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘17.0.13’

Driver info: io.appium.java_client.android.AndroidDriver

Command: [null, newSession {capabilities=[Capabilities {appium:app: E:\OneDrive - Apsi…, appium:autoGrantPermissions: true, appium:automationName: UiAutomator2, appium:deviceId: , appium:deviceName: R58RB1K2ZJT, appium:fullReset: false, appium:newCommandTimeout: 300.0, appium:noReset: true, appium:platformName: Android, appium:platformVersion: 13, appium:systemPort: 8764, appium:udid: R58RB1K2ZJT, platformName: ANDROID}]}]

Capabilities {appium:app: E:\OneDrive - Apsi…, appium:autoGrantPermissions: true, appium:automationName: UiAutomator2, appium:deviceId: , appium:deviceName: R58RB1K2ZJT, appium:fullReset: false, appium:newCommandTimeout: 300.0, appium:noReset: true, appium:platformName: Android, appium:platformVersion: 13, appium:systemPort: 8764, appium:udid: R58RB1K2ZJT, platformName: ANDROID}

at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:114)

at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:75)

at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:61)

at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:176)

at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:237)

at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:518)

at io.appium.java_client.AppiumDriver.startSession(AppiumDriver.java:270)

at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:161)

at io.appium.java_client.AppiumDriver.(AppiumDriver.java:91)

at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:99)

at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:574)

at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:551)

at com.kms.katalon.core.mobile.keyword.internal.MobileDriverFactory.startLocalMobileDriver(MobileDriverFactory.java:597)

at com.kms.katalon.core.mobile.keyword.internal.MobileDriverFactory.startMobileDriver(MobileDriverFactory.java:510)

at com.kms.katalon.core.mobile.keyword.builtin.StartApplicationKeyword$_startApplication_closure1.doCall(StartApplicationKeyword.groovy:89)

at com.kms.katalon.core.mobile.keyword.builtin.StartApplicationKeyword$_startApplication_closure1.call(StartApplicationKeyword.groovy)

at com.kms.katalon.core.mobile.keyword.internal.MobileKeywordMain.runKeyword(MobileKeywordMain.groovy:30)

… 18 more

Still the same issue shows after installing the `UiAutomator2 driver