Running Script on Mobile Browser

Ameet_Thakkar · October 28, 2019, 9:54pm

Hello Team,

I am referring to the technote : https://docs.katalon.com/katalon-studio/docs/running_application_mobile_browsers.html#what-youll-learn

So i tried exactly using the script mentioned in the link and execute on Web(Chrome) browser and it works fine.

Then, I have connected by local (Andriod) device and added the desired capabilities and I can see the device in ADB, as well under Play button (Android) the script runs fine on the mobile browser to the point where it opens the website and navigates to url.
However when trying to setText it fails

===

2019-10-28 17:42:37.968 ERROR c.k.katalon.core.main.TestCaseExecutor - Test Cases/MobileWebBrowser FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Unable to set text ‘John Doe’ of object ‘Object Repository/Demo-Katalon/Page_CURA Healthcare Service/input_Username_username’
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26)
at com.kms.katalon.core.webui.keyword.builtin.SetTextKeyword.setText(SetTextKeyword.groovy:66)
at com.kms.katalon.core.webui.keyword.builtin.SetTextKeyword.execute(SetTextKeyword.groovy:37)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.setText(WebUiBuiltInKeywords.groovy:950)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$setText$6.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:51)
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:337)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:114)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:105)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1572298842585.run(TempTestCase1572298842585.groovy:23)
Caused by: org.openqa.selenium.WebDriverException: unknown error: call function result missing ‘value’
(Session info: chrome=78.0.3904.62)
(Driver info: chromedriver=2.30.477700 (0057494ad8732195794a7b32078424f92a5fce41),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

===

So not sure what is missing but it is stuck up and I need your help to move to be able to set the text on the user name and then password as the same way it works on the Web Browser.

ThanhTo · November 13, 2019, 6:50am

Hi @Ameet_Thakkar

Can you tell me what version of Katalon Studio are you using ? What about the ChromeDriver version and the Chrome browser version on the device you’re using. I ask since there’s an StackOverflow answer that may provide the hints:

Ameet_Thakkar · November 13, 2019, 8:27pm

Hello Thanh To,

Many thanks to you for reverting back.

I am using Katalon Studio v 7.0.0

I am using
a) Locally connected Samsung Galaxy S9 device.
Appium version is 1.15.1

When i run the script i get the below error.

2019-11-13 15:20:01.220 INFO c.k.katalon.core.main.TestCaseExecutor - --------------------
2019-11-13 15:20:01.226 INFO c.k.katalon.core.main.TestCaseExecutor - START Test Cases/MobileWebBrowser
2019-11-13 15:20:02.471 DEBUG testcase.MobileWebBrowser - 1: openBrowser("")
2019-11-13 15:20:02.951 INFO c.k.k.core.webui.driver.DriverFactory - Starting ‘Android’ driver
2019-11-13 15:20:03.054 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘browserName’, ‘chrome’]
2019-11-13 15:20:03.060 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: ['version ', ‘’]
2019-11-13 15:20:03.062 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘platformName’, ‘ANDROID’]
2019-11-13 15:20:03.063 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘platformVersion’, ‘9.0’]
2019-11-13 15:20:03.064 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘deviceName’, ‘4b4549534c573398’]
2019-11-13 15:20:03.065 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘unicodeKeyboard’, ‘true’]
2019-11-13 15:20:03.065 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘automationName’, ‘UiAutomator2’]
2019-11-13 15:20:03.066 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘deviceId’, ‘’]
2019-11-13 15:20:10.308 INFO c.k.k.c.a.driver.AppiumDriverManager - Appium server started on port 51,028
e[35m[Appium]e[39m Welcome to Appium v1.15.1
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 51028
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 51030
e[35m[Appium]e[39m tmpDir: C:\Users\at275j\AppData\Local\Temp\Katalon\Appium\Temp1573676403105
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:51028
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m5 ms - 68e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“newCommandTimeout”:1800,“platformVersion”:“9.0”,“automationName”:“UiAutomator2”,“browserName”:“Chrome”,“unicodeKeyboard”:true,“platformName”:“Android”,“udid”:“4b4549534c573398”,“deviceId”:"",“deviceName”:“test”,“platform”:“ANDROID”,“version\t”:""},“capabilities”:{“firstMatch”:[{“appium:automationName”:“UiAutomator2”,“browserName”:“Chrome”,“deviceId”:"",“appium:deviceName”:“test”,“appium:newCommandTimeout”:1800,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“9.0”,“appium:udid”:“4b4549534c573398”,“appium:unicodeKeyboard”:true,“version\t”:""}]}}e[39m
e[35m[BaseDriver]e[39m The capabilities [“deviceId”,“platform”,“version\t”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m Appium v1.15.1 creating new AndroidUiautomator2Driver (v1.37.2) session
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
e[35m[BaseDriver]e[39m deviceId
e[35m[BaseDriver]e[39m platform
e[35m[BaseDriver]e[39m version
e[35m[BaseDriver]e[39m Session created with session id: bdd7e8e2-7b4a-4bad-b5ab-16b005a1a9e2
e[35m[UiAutomator2]e[39m We’re going to run a Chrome-based session
e[35m[UiAutomator2]e[39m Chrome-type package and activity are com.android.chrome and com.google.android.apps.chrome.Main
e[35m[UiAutomator2]e[39m Starting ‘com.android.chrome’ directly on the device
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\at275j.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/at275j/.katalon/tools/android_sdk/build-tools/29.0.2
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: 4b4549534c573398
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[UiAutomator2]e[39m Relaxing hidden api policy
e[35m[AndroidDriver]e[39m No app sent in, not parsing package/activity
e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\build-tools\29.0.2\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\at275j.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\build-tools\29.0.2\aapt.exe’
e[35m[ADB]e[39m Caching the application at ‘C:\BuildAgent\npm\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk’ to ‘/data/local/tmp/appium_cache/3d97225b036c28750562ef8962defee6b1af19a4.apk’
e[35m[ADB]e[39m The upload of ‘settings_apk-debug.apk’ (1.16 MB) took 1.865s
e[35m[ADB]e[39m The installation of ‘settings_apk-debug.apk’ took 7.275s
e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\at275j\.katalon\tools\android_sdk\build-tools\29.0.2\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\at275j.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\at275j.katalon\tools\android_sdk\build-tools\29.0.2\apksigner.bat’
e[35m[UiAutomator2]e[39m Server packages are going to be (re)installed
e[35m[UiAutomator2]e[39m Full packages reinstall is going to be performed
e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled
e[35m[ADB]e[39m Caching the application at ‘C:\BuildAgent\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ to ‘/data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’
e[35m[ADB]e[39m The upload of ‘appium-uiautomator2-server-v4.3.0.apk’ (2.14 MB) took 1.507s
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v4.3.0.apk’ took 8.577s
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
e[35m[ADB]e[39m Caching the application at ‘C:\BuildAgent\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ to ‘/data/local/tmp/appium_cache/cd247f042368990c9f33b2d7bf2390d8cf4f4e24.apk’
e[35m[ADB]e[39m The upload of ‘appium-uiautomator2-server-debug-androidTest.apk’ (539.10 KB) took 1.267s
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 5.350s
e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 4.3.0
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\BuildAgent\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ and test from ‘C:\BuildAgent\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
e[35m[WD Proxy]e[39m Got an unexpected response with status undefined: {“code”:“ECONNRESET”}
e[35m[WD Proxy]e[39m Got an unexpected response with status undefined: {“code”:“ECONNRESET”}
e[35m[WD Proxy]e[39m Got an unexpected response with status undefined: {“code”:“ECONNRESET”}
e[35m[WD Proxy]e[39m Determined the downstream protocol as ‘W3C’
e[35m[AndroidDriver]e[39m Screen already unlocked, doing nothing
e[35m[AndroidDriver]e[39m Starting a chrome-based browser session
e[35m[AndroidDriver]e[39m The ‘chromeDriverPort’ capability is deprecated. Please use ‘chromedriverPort’ instead
e[35m[UiAutomator2]e[39m Restoring hidden api policy to the device default configuration
2019-11-13 15:21:21.212 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceId = 4b4549534c573398
2019-11-13 15:21:21.213 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceName = samsung SM-G960U1 (Android 9)
2019-11-13 15:21:21.214 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceModel = SM-G960U1
2019-11-13 15:21:21.215 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceManufacturer = samsung
2019-11-13 15:21:21.217 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOS = Android
2019-11-13 15:21:21.218 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOSVersion = 9
2019-11-13 15:21:21.246 ERROR c.k.k.core.keyword.internal.KeywordMain - Unable to open browser with url: ‘’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:26)
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:337)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:114)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:105)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1573676393387.run(TempTestCase1573676393387.groovy:23)
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: No Chromedriver found that can automate Chrome ‘78.0.3904’. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details. You could also try to enable automated chromedrivers download server feature
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.208.128’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: No Chromedriver found that can automate Chrome ‘78.0.3904’. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details. You could also try to enable automated chromedrivers download server feature
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:804:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:388:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.208.128’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:208)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:217)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:239)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.execute(SwipeableAndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:84)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:85)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.(SwipeableAndroidDriver.java:24)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:497)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:479)
at com.kms.katalon.core.webui.driver.WebMobileDriverFactory.createMobileDriver(WebMobileDriverFactory.java:132)
at com.kms.katalon.core.webui.driver.DriverFactory.startNewBrowser(DriverFactory.java:316)
at com.kms.katalon.core.webui.driver.DriverFactory.openWebDriver(DriverFactory.java:206)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.doCall(OpenBrowserKeyword.groovy:74)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.call(OpenBrowserKeyword.groovy)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:20)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at Script1572025859697.run(Script1572025859697.groovy:26)
… 11 more
Caused by: java.lang.reflect.InvocationTargetException
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:186)
… 38 more

I have followed this link : https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md

to upadate the chrome driver but still no success… May be i am missing something here.

ThanhTo · November 14, 2019, 3:07am

Hi @Ameet_Thakkar

There’s a bug report on Appium that may be of interests:

Try to downgrade appium and then install the appropriate driver version again to see if it works.

Ameet_Thakkar · November 14, 2019, 4:53pm

Hi ThanhTo,

Many thanks for your soln

npm install -g appium@1.14.1 --chromedriver_version=“2.42” did the trick for me.

You were right.
I was able to downgrade the appium and chromedriver… as per above link… and it worked.

I am able to execute the script on a local device(Android- usb connected) successfully.

------

Ameet_Thakkar · November 14, 2019, 4:55pm

However my second part of problem is:

I have a remote Android Device ( which i can connected locally using the deviceBridge Feature of Mobile labs )

I want to target this same script on that device.
I can see the device on my adb.
However when i run the script it gives me the error

Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.253.202’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code:

So any idea how to fix that issue.

ThanhTo · November 14, 2019, 5:15pm

Hi @Ameet_Thakkar

Please post the full log, I don’t think what you posted is enough to know where the problem is.

Ameet_Thakkar · November 14, 2019, 5:51pm

There are few things that i wish to share with you for further troubleshooting.

a) Image shows the device ADB connected locally ( because of the deviceBridge feature of Mobile labs )

b) While trying to run(execute the script ) It is trying to target the device, but looks like earlier time stamp of the device is still there… and may be because of that the error. ( my guess)

c) in the project–settings- i can’t see that device yet… however i did manually change the device ID as you can see… but the new device is not there yet…

Here’s the complete log of the error

2019-11-14 12:42:31.693 INFO c.k.katalon.core.main.TestCaseExecutor - --------------------
2019-11-14 12:42:31.702 INFO c.k.katalon.core.main.TestCaseExecutor - START Test Cases/MobileWebBrowser
2019-11-14 12:42:33.996 DEBUG testcase.MobileWebBrowser - 1: openBrowser("")
2019-11-14 12:42:35.092 INFO c.k.k.core.webui.driver.DriverFactory - Starting ‘Android’ driver
2019-11-14 12:42:35.302 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘browserName’, ‘chrome’]
2019-11-14 12:42:35.304 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: ['version ', ‘’]
2019-11-14 12:42:35.306 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘platformName’, ‘ANDROID’]
2019-11-14 12:42:35.307 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘platformVersion’, ‘6.0.1’]
2019-11-14 12:42:35.309 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘deviceName’, ‘fd5ac8b4’]
2019-11-14 12:42:35.310 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘unicodeKeyboard’, ‘true’]
2019-11-14 12:42:35.312 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘automationName’, ‘UiAutomator2’]
2019-11-14 12:42:35.313 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘deviceId’, ‘’]
e[35m[Appium]e[39m Welcome to Appium v1.14.1
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 52144
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 52158
e[35m[Appium]e[39m tmpDir: C:\Users\at275j\AppData\Local\Temp\Katalon\Appium\Temp1573753355366
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:52144
2019-11-14 12:42:49.360 INFO c.k.k.c.a.driver.AppiumDriverManager - Appium server started on port 52,144
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m11 ms - 68e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“newCommandTimeout”:1800,“platformVersion”:“6.0.1”,“automationName”:“UiAutomator2”,“browserName”:“Chrome”,“unicodeKeyboard”:true,“platformName”:“Android”,“udid”:“fd5ac8b4”,“deviceId”:"",“deviceName”:“test”,“platform”:“ANDROID”,“version\t”:""},“capabilities”:{“firstMatch”:[{“appium:automationName”:“UiAutomator2”,“browserName”:“Chrome”,“deviceId”:"",“appium:deviceName”:“test”,“appium:newCommandTimeout”:1800,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“6.0.1”,“appium:udid”:“fd5ac8b4”,“appium:unicodeKeyboard”:true,“version\t”:""}]}}e[39m
e[35m[BaseDriver]e[39m The capabilities [“deviceId”,“platform”,“version\t”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m Appium v1.14.1 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m browserName: Chrome
e[35m[Appium]e[39m deviceId:
e[35m[Appium]e[39m platform: ANDROID
e[35m[Appium]e[39m platformName: android
e[35m[Appium]e[39m version :
e[35m[Appium]e[39m automationName: UiAutomator2
e[35m[Appium]e[39m deviceName: test
e[35m[Appium]e[39m newCommandTimeout: 1800
e[35m[Appium]e[39m platformVersion: 6.0.1
e[35m[Appium]e[39m udid: fd5ac8b4
e[35m[Appium]e[39m unicodeKeyboard: true
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: deviceId, platform, version .
e[35m[BaseDriver]e[39m Session created with session id: c28dd112-e89a-4cf6-a312-24183a4dabac
e[35m[UiAutomator2]e[39m We’re going to run a Chrome-based session
e[35m[UiAutomator2]e[39m Chrome-type package and activity are com.android.chrome and com.google.android.apps.chrome.Main
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\at275j.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/at275j/.katalon/tools/android_sdk/build-tools/29.0.2
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: fd5ac8b4
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m No app sent in, not parsing package/activity
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\build-tools\29.0.2\aapt.exe’
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\at275j.katalon\tools\android_sdk\build-tools\29.0.2\apksigner.bat’
e[35m[UiAutomator2]e[39m Server packages are not going to be (re)installed
e[35m[UiAutomator2]e[39m Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
e[35m[UiAutomator2]e[39m Unable to remove port forward ‘Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward --remove tcp:8200’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’’
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m48660 ms - 1077e[39m
e[35m[HTTP]e[39m e[90me[39m
2019-11-14 12:43:40.413 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceId = fd5ac8b4
2019-11-14 12:43:40.414 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceName = samsung SAMSUNG-SM-N910A (Android 6.0.1)
2019-11-14 12:43:40.415 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceModel = SAMSUNG-SM-N910A
2019-11-14 12:43:40.417 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceManufacturer = samsung
2019-11-14 12:43:40.419 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOS = Android
2019-11-14 12:43:40.421 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOSVersion = 6.0.1
2019-11-14 12:43:40.451 ERROR c.k.k.core.keyword.internal.KeywordMain - Unable to open browser with url: ‘’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:26)
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:337)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:114)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:105)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1573753340998.run(TempTestCase1573753340998.groovy:23)
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: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.231.20’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.231.20’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:208)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:217)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:239)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.execute(SwipeableAndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:84)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:85)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.(SwipeableAndroidDriver.java:24)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:497)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:479)
at com.kms.katalon.core.webui.driver.WebMobileDriverFactory.createMobileDriver(WebMobileDriverFactory.java:132)
at com.kms.katalon.core.webui.driver.DriverFactory.startNewBrowser(DriverFactory.java:316)
at com.kms.katalon.core.webui.driver.DriverFactory.openWebDriver(DriverFactory.java:206)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.doCall(OpenBrowserKeyword.groovy:74)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.call(OpenBrowserKeyword.groovy)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:20)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at Script1572025859697.run(Script1572025859697.groovy:26)
… 11 more
Caused by: java.lang.reflect.InvocationTargetException
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:186)
… 38 more
Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.231.20’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
at org.openqa.selenium.remote.W3CHandshakeResponse.lambda$errorHandler$0(W3CHandshakeResponse.java:62)
at org.openqa.selenium.remote.HandshakeResponse.lambda$getResponseFunction$0(HandshakeResponse.java:30)
at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:126)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:128)
… 39 more
)
2019-11-14 12:43:40.475 ERROR c.k.katalon.core.main.TestCaseExecutor - Test Cases/MobileWebBrowser FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:26)
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:337)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:114)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:105)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1573753340998.run(TempTestCase1573753340998.groovy:23)
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: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.231.20’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.231.20’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:208)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:217)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:239)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.execute(SwipeableAndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:84)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:85)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.(SwipeableAndroidDriver.java:24)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:497)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:479)
at com.kms.katalon.core.webui.driver.WebMobileDriverFactory.createMobileDriver(WebMobileDriverFactory.java:132)
at com.kms.katalon.core.webui.driver.DriverFactory.startNewBrowser(DriverFactory.java:316)
at com.kms.katalon.core.webui.driver.DriverFactory.openWebDriver(DriverFactory.java:206)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.doCall(OpenBrowserKeyword.groovy:74)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.call(OpenBrowserKeyword.groovy)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:20)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at Script1572025859697.run(Script1572025859697.groovy:26)
… 11 more
Caused by: java.lang.reflect.InvocationTargetException
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:186)
… 38 more
Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘135.70.231.20’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
at org.openqa.selenium.remote.W3CHandshakeResponse.lambda$errorHandler$0(W3CHandshakeResponse.java:62)
at org.openqa.selenium.remote.HandshakeResponse.lambda$getResponseFunction$0(HandshakeResponse.java:30)
at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:126)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:128)
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:186)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:217)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:239)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.execute(SwipeableAndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:84)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:85)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.(SwipeableAndroidDriver.java:24)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:497)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:479)
at com.kms.katalon.core.webui.driver.WebMobileDriverFactory.createMobileDriver(WebMobileDriverFactory.java:132)
at com.kms.katalon.core.webui.driver.DriverFactory.startNewBrowser(DriverFactory.java:316)
at com.kms.katalon.core.webui.driver.DriverFactory.openWebDriver(DriverFactory.java:206)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.doCall(OpenBrowserKeyword.groovy:74)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.call(OpenBrowserKeyword.groovy)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:20)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:26)
… 11 more

2019-11-14 12:43:40.501 INFO c.k.katalon.core.main.TestCaseExecutor - END Test Cases/MobileWebBrowser

ThanhTo · November 15, 2019, 3:26am

I don’t think that is the deviceName, can you try to replace it by deviceId ?

duyluong · November 15, 2019, 4:58am

@Ameet_Thakkar,

Please remove deviceName property in Desired Capabities, Katalon Studio will automatically fill in this property.

Thanks

Ameet_Thakkar · November 15, 2019, 4:14pm

Thank you for the inputs… I remove the deviceName and add deviceId, But still no success

the script execution error is

2019-11-15 11:11:18.428 INFO c.k.katalon.core.main.TestCaseExecutor - --------------------
2019-11-15 11:11:18.436 INFO c.k.katalon.core.main.TestCaseExecutor - START Test Cases/MobileWebBrowser
2019-11-15 11:11:21.192 DEBUG testcase.MobileWebBrowser - 1: openBrowser("")
2019-11-15 11:11:22.109 INFO c.k.k.core.webui.driver.DriverFactory - Starting ‘Android’ driver
2019-11-15 11:11:22.286 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘browserName’, ‘chrome’]
2019-11-15 11:11:22.288 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: ['version ', ‘’]
2019-11-15 11:11:22.290 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘platformName’, ‘ANDROID’]
2019-11-15 11:11:22.291 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘platformVersion’, ‘6.0.1’]
2019-11-15 11:11:22.292 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘unicodeKeyboard’, ‘true’]
2019-11-15 11:11:22.293 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘automationName’, ‘UiAutomator2’]
2019-11-15 11:11:22.294 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘deviceID’, ‘’]
2019-11-15 11:11:22.295 INFO c.k.k.c.w.driver.WebMobileDriverFactory - User set preference: [‘deviceId’, ‘’]
e[35m[Appium]e[39m Welcome to Appium v1.14.1
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 57143
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 57189
e[35m[Appium]e[39m tmpDir: C:\Users\at275j\AppData\Local\Temp\Katalon\Appium\Temp1573834282351
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:57143
2019-11-15 11:11:36.585 INFO c.k.k.c.a.driver.AppiumDriverManager - Appium server started on port 57,143
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m7 ms - 68e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“deviceID”:"",“deviceId”:"",“deviceName”:“test”,“platform”:“ANDROID”,“newCommandTimeout”:1800,“platformVersion”:“6.0.1”,“automationName”:“UiAutomator2”,“browserName”:“Chrome”,“unicodeKeyboard”:true,“platformName”:“Android”,“udid”:“fd5ac8b4”,“version\t”:""},“capabilities”:{“firstMatch”:[{“appium:automationName”:“UiAutomator2”,“browserName”:“Chrome”,“deviceID”:"",“deviceId”:"",“appium:deviceName”:“test”,“appium:newCommandTimeout”:1800,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“6.0.1”,“appium:udid”:“fd5ac8b4”,“appium:unicodeKeyboard”:true,“version\t”:""}]}}e[39m
e[35m[BaseDriver]e[39m The capabilities [“deviceID”,“deviceId”,“platform”,“version\t”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m Appium v1.14.1 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m browserName: Chrome
e[35m[Appium]e[39m deviceID:
e[35m[Appium]e[39m deviceId:
e[35m[Appium]e[39m platform: ANDROID
e[35m[Appium]e[39m platformName: android
e[35m[Appium]e[39m version :
e[35m[Appium]e[39m automationName: UiAutomator2
e[35m[Appium]e[39m deviceName: test
e[35m[Appium]e[39m newCommandTimeout: 1800
e[35m[Appium]e[39m platformVersion: 6.0.1
e[35m[Appium]e[39m udid: fd5ac8b4
e[35m[Appium]e[39m unicodeKeyboard: true
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: deviceID, deviceId, platform, version .
e[35m[BaseDriver]e[39m Session created with session id: 0501a29a-509a-40e5-bb7c-61e7de400f8d
e[35m[UiAutomator2]e[39m We’re going to run a Chrome-based session
e[35m[UiAutomator2]e[39m Chrome-type package and activity are com.android.chrome and com.google.android.apps.chrome.Main
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\at275j.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/at275j/.katalon/tools/android_sdk/build-tools/29.0.2
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: fd5ac8b4
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m No app sent in, not parsing package/activity
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\at275j.katalon\tools\android_sdk\build-tools\29.0.2\aapt.exe’
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\at275j.katalon\tools\android_sdk\build-tools\29.0.2\apksigner.bat’
e[35m[UiAutomator2]e[39m Server packages are not going to be (re)installed
e[35m[UiAutomator2]e[39m Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
2019-11-15 11:12:43.312 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceId = fd5ac8b4
2019-11-15 11:12:43.335 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceName = samsung SAMSUNG-SM-N910A (Android 6.0.1)
2019-11-15 11:12:43.337 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceModel = SAMSUNG-SM-N910A
2019-11-15 11:12:43.343 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceManufacturer = samsung
2019-11-15 11:12:43.345 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOS = Android
2019-11-15 11:12:43.349 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOSVersion = 6.0.1
e[35m[UiAutomator2]e[39m Unable to remove port forward ‘Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward --remove tcp:8200’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’’
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m58599 ms - 1077e[39m
e[35m[HTTP]e[39m e[90me[39m
2019-11-15 11:12:43.758 ERROR c.k.k.core.keyword.internal.KeywordMain - Unable to open browser with url: ‘’ (Root cause: com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:26)
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:337)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:114)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:105)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1573834266562.run(TempTestCase1573834266562.groovy:23)
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: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘130.10.236.93’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘130.10.236.93’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:208)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:217)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:239)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.execute(SwipeableAndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:84)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:85)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.(SwipeableAndroidDriver.java:24)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:497)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:479)
at com.kms.katalon.core.webui.driver.WebMobileDriverFactory.createMobileDriver(WebMobileDriverFactory.java:132)
at com.kms.katalon.core.webui.driver.DriverFactory.startNewBrowser(DriverFactory.java:316)
at com.kms.katalon.core.webui.driver.DriverFactory.openWebDriver(DriverFactory.java:206)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.doCall(OpenBrowserKeyword.groovy:74)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.call(OpenBrowserKeyword.groovy)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:20)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at Script1572025859697.run(Script1572025859697.groovy:26)
… 11 more
Caused by: java.lang.reflect.InvocationTargetException
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:186)
… 38 more
Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘130.10.236.93’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
at org.openqa.selenium.remote.W3CHandshakeResponse.lambda$errorHandler$0(W3CHandshakeResponse.java:62)
at org.openqa.selenium.remote.HandshakeResponse.lambda$getResponseFunction$0(HandshakeResponse.java:30)
at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:126)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:128)
… 39 more
)
2019-11-15 11:12:43.930 ERROR c.k.katalon.core.main.TestCaseExecutor - Test Cases/MobileWebBrowser FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:64)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:26)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at MobileWebBrowser.run(MobileWebBrowser:26)
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:337)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:307)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:299)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:233)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:114)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:105)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1573834266562.run(TempTestCase1573834266562.groovy:23)
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: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘130.10.236.93’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\at275j\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: more than one device/emulator’; Code: ‘1’
at getResponseForW3CError (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\BuildAgent\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘GACDTL02AT275J’, ip: ‘130.10.236.93’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:208)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:217)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:239)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:42)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.execute(SwipeableAndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at io.appium.java_client.DefaultGenericMobileDriver.(DefaultGenericMobileDriver.java:38)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:84)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:85)
at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.(SwipeableAndroidDriver.java:24)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:497)
at com.kms.katalon.core.appium.driver.AppiumDriverManager.createMobileDriver(AppiumDriverManager.java:479)
at com.kms.katalon.core.webui.driver.WebMobileDriverFactory.createMobileDriver(WebMobileDriverFactory.java:132)
at com.kms.katalon.core.webui.driver.DriverFactory.startNewBrowser(DriverFactory.java:316)
at com.kms.katalon.core.webui.driver.DriverFactory.openWebDriver(DriverFactory.java:206)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.doCall(OpenBrowserKeyword.groovy:74)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword$_openBrowser_closure1.call(OpenBrowserKeyword.groovy)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:20)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at Script1572025859697.run(Script1572025859697.groovy:26)
… 11 more
Caused by: java.lang.reflect.InvocationTargetException
at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:186)
… 38 more

ThanhTo · November 15, 2019, 5:15pm

Please show us the console’s content after running:

C:\Users\at275j.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s fd5ac8b4 forward --remove
tcp:8200

in your terminal/windows console.

neha.dua.2 · May 22, 2020, 3:03pm

Hi AMit ,

I am also working on Katalon Mobile AUtomation with device available on Gifa fox mobile lab.
I am able to connect to device but when I am passing browser chrome , it’s throwing W3C error.
Then I found on web that its need to set false in Chrome desired capabilities.
DO you have any idea when we are working with remote device , how we can set capabilities for browser ?
For appium we are able to pass capabilities under Remote option in project settings.

Exception:
java.util.concurrent.ExecutionException: org.openqa.selenium.UnsupportedCommandException: unknown command: Cannot call non W3C standard command while in W3C mode (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’
System info: host: ‘XDW10IMPDWGS266’, ip: ‘10.64.235.53’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘1.8.0_181’
Driver info: com.kms.katalon.core.appium.driver.SwipeableAndroidDriver
Capabilities {DatabaseEnabled: false, JavascriptEnabled: true, LocationContextEnabled: false, Platform: LINUX, TakesScreenshot: true, WebStorageEnabled: false, appActivity: com.google.android.apps.chr…, appPackage: com.android.chrome, automationName: uiautomator2, browserName: Chrome, chromedriverPort: 23258, deviceName: RF8MA33JQYX, javascriptEnabled: true, platform: ANDROID, platformName: Android, platformVersion: 10, skipServerInstallation: true, systemPort: 23108, udid: RF8MA33JQYX}
Session ID: a11a3163-a0f4-4fce-a619-d17d5e8d33b7
at com.kms.katalon.composer.components.impl.dialogs.ProgressMonitorDialogWithThread.runAndWait(ProgressMonitorDialogWithThread.java:49)
at com.kms.katalon.composer.mobile.objectspy.components.RemoteAppComposite$1.run(RemoteAppComposite.java:112)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Caused by: org.openqa.selenium.UnsupportedCommandException: unknown command: Cannot call non W3C standard command while in W3C mode (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’
System info: host: ‘XDW10IMPDWGS266’, ip: ‘10.64.235.53’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘1.8.0_181’
Driver info: com.kms.katalon.core.appium.driver.SwipeableAndroidDriver
Capabilities {DatabaseEnabled: false, JavascriptEnabled: true, LocationContextEnabled: false, Platform: LINUX, TakesScreenshot: true, WebStorageEnabled: false, appActivity: com.google.android.apps.chr…, appPackage: com.android.chrome, automationName: uiautomator2, browserName: Chrome, chromedriverPort: 23258, deviceName: RF8MA33JQYX, javascriptEnabled: true, platform: ANDROID, platformName: Android, platformVersion: 10, skipServerInstallation: true, systemPort: 23108, udid: RF8MA33JQYX}
Session ID: a11a3163-a0f4-4fce-a619-d17d5e8d33b7

Jass · June 15, 2020, 4:18am