Katalon Studio version 6.2.0.rc1 with experimental support for iOS 12.2 and Xcode 10.2

Product Forums Katalon Studio
, ,
1

Update: https://github.com/katalon-studio/katalon-studio/releases/tag/v6.2.0.rc5

Update: https://github.com/katalon-studio/katalon-studio/releases/tag/v6.2.0.rc4

Katalon Studio version 6.2.0.rc1 with experimental support for iOS 12.2 and Xcode 10.2.

https://s3.amazonaws.com/katalon/release-beta/6.2.0.rc1/Katalon+Studio.app.zip
https://s3.amazonaws.com/katalon/release-beta/6.2.0.rc1/Katalon+Studio.dmg
https://s3.amazonaws.com/katalon/release-beta/6.2.0.rc1/Katalon_Studio_Linux_64-6.2.0.tar.gz
https://s3.amazonaws.com/katalon/release-beta/6.2.0.rc1/Katalon_Studio_Windows_32-6.2.0.zip
https://s3.amazonaws.com/katalon/release-beta/6.2.0.rc1/Katalon_Studio_Windows_64-6.2.0.zip

Instruction to upgrade Appium from 1.8.1 to 1.12.1 for Android testing user

  • Manually remove io.appium.uiautomator2.server.test and appium.uiautomator2.server from your devices.
  • Manually delete folder <user_folder>/.katalon/tools/android_sdk.

Support iOS 12.2 and Xcode 10.2

Changes and Improvements:

General

  • Update selenium-standalone-server from 3.7.1 to 3.141.59

Mobile

  • Update appium-java-client from 5.0.0 to 7.0.0
  • Support appium v1.12.1
  • Support iOS 12.2 and Xcode 10.2
  • Remove embedded carthage, libimobiledevice, and ios-deploy

Requirement for testing iOS application 12.2

  • Appium v1.12.1
  • Xcode 10.2 for iOS 12.2
  • Carthage 0.33 or later
  • ios-deploy 1.9.4 or later
  • ios-webkit-debug-proxy 1.8.4 or later
  • libimobiledevice 1.2.0 or later
  • usbmuxd 1.0.10 or later

Instruction for installing Appium v1.12.1 or later and other requirements:

Install appium:

npm install -g appium

Install homebrew:

Install carthage

brew install carthage

Install ios-deploy

brew install ios-deploy

Install usbmuxd

sudo chmod -R 777 /var/db/lockdown/
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd

Install ios-webkit-debug-proxy

brew install ios-webkit-debug-proxy

Install libimobiledevice

brew install --HEAD libimobiledevice
brew unlink libimobiledevice
brew link libimobiledevice

Install WebDriverAgent

3 Likes
7

Custom timeouts (specified when calling a keyword, e.g. tap) do not work. If i use Mobile.tap() with a timeout of 5 seconds and FailureHandling.OPTIONAL, it will wait the whole timeout of 30 seconds.

2 Likes
8

Hello,

I tested the new release since our focus is on the iOS 12.2 and XCode 10.2, The first step was to confirm 6.2.0 rc1 works with Android and Appium Desktop 1.12.1. After installing Appium Desktop 1.12.1 I executed the Android Demo app Verify Last Items In List. The application failed to start. We use Appium desktop instead of installing via NPM. Is the desktop version support with 6.2.0 RC1?

Thank you, Paul

The details on my testing are shown below:
I am working with the Katalon 6.2.0 RC1 and found that using Appium Desktop 1.6.1 installed from the Appium site ( https://github.com/appium/appium-desktop/releases/tag/v1.6.1 ) that the Demo test Verify Last Items In List works on the Android Emulator. When I install Appium Desktop 1.12.1 the application fails to start and presents the information in the table below.

Appium Desktop 1.12.1
04-10-2019 07:53:12 AM Test Cases/Verify Last Items In List

Elapsed time: 27.199s

Test Cases/Verify Last Items In List FAILED.

Reason:

com.kms.katalon.core.exception.StepFailedException: Unable to start app at: ‘C:\Users\pkanaris\Katalon Studio\Katalon_Android_sample.prj\androidapp\APIDemos.apk’ (Root cause: 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: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’

System info: host: ‘KSD-FG6J7UQ’, ip: ‘10.119.120.119’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, 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: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

at getResponseForW3CError (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)

at asyncHandler (C:\Program Files\Appium\resources\app\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: ‘KSD-FG6J7UQ’, ip: ‘10.119.120.119’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, 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.<init>(RemoteWebDriver.java:131)

at io.appium.java_client.DefaultGenericMobileDriver.<init>(DefaultGenericMobileDriver.java:38)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:84)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:94)

at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:95)

at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.<init>(SwipeableAndroidDriver.java:19)

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

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

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

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

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

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:21)

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

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

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

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

at com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords$startApplication.call(Unknown Source)

at Verify Last Items In List.run(Verify Last Items In List: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:342)

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

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

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

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

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 TempTestCase1554897188357.run(TempTestCase1554897188357.groovy:21)

Caused by: java.lang.reflect.InvocationTargetException

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.<init>(RemoteWebDriver.java:131)

at io.appium.java_client.DefaultGenericMobileDriver.<init>(DefaultGenericMobileDriver.java:38)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:84)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:94)

at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:95)

at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.<init>(SwipeableAndroidDriver.java:19)

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

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

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

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

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

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:21)

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

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

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

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

at com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords$startApplication.call(Unknown Source)

at Script1529986164129.run(Script1529986164129.groovy:16)

… 11 more

Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’

System info: host: ‘KSD-FG6J7UQ’, ip: ‘10.119.120.119’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, 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: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

at getResponseForW3CError (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)

at asyncHandler (C:\Program Files\Appium\resources\app\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

)

at com.kms.katalon.core.keyword.internal.KeywordMain.stepFailed(KeywordMain.groovy:48)

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

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

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

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

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

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

at com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords$startApplication.call(Unknown Source)

at Verify Last Items In List.run(Verify Last Items In List: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:342)

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

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

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

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

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 TempTestCase1554897188357.run(TempTestCase1554897188357.groovy:21)

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: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’

System info: host: ‘KSD-FG6J7UQ’, ip: ‘10.119.120.119’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, 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: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

at getResponseForW3CError (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)

at asyncHandler (C:\Program Files\Appium\resources\app\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: ‘KSD-FG6J7UQ’, ip: ‘10.119.120.119’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, 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.<init>(RemoteWebDriver.java:131)

at io.appium.java_client.DefaultGenericMobileDriver.<init>(DefaultGenericMobileDriver.java:38)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:84)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:94)

at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:95)

at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.<init>(SwipeableAndroidDriver.java:19)

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

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

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

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

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

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:21)

… 17 more

Caused by: java.lang.reflect.InvocationTargetException

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.<init>(RemoteWebDriver.java:131)

at io.appium.java_client.DefaultGenericMobileDriver.<init>(DefaultGenericMobileDriver.java:38)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:84)

at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:94)

at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:95)

at com.kms.katalon.core.appium.driver.SwipeableAndroidDriver.<init>(SwipeableAndroidDriver.java:19)

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

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

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

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

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

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:21)

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

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

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

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

at com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords$startApplication.call(Unknown Source)

at Script1529986164129.run(Script1529986164129.groovy:16)

… 11 more

Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’

System info: host: ‘KSD-FG6J7UQ’, ip: ‘10.119.120.119’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, 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: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

at getResponseForW3CError (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)

at asyncHandler (C:\Program Files\Appium\resources\app\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

9

Hi,

I am having the same issues as Paul_Kanaris with Win10, npm Appium 1.12.1 and Android.

• Katalon Studio : The instrumentation process cannot be initialized.

• ADB logcat : Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/android.support.test.runner.AndroidJUnitRunner} from pid=*** uid=**** not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server (I tried to uninstall it manually but it still gives the same error)

I have rollback to npm Appium 1.8.1 and I now get an error only with the version 6.2 when using tapAtPosition (S7 Android 8.0).

device_Height = Mobile.getDeviceHeight()
device_Width = Mobile.getDeviceWidth()

• ERROR c.k.katalon.core.main.TestCaseExecutor - :x: tapAtPosition(device_Height * 0.40, device_Width * 0.50) FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Failed to tap at [1,024, 720] (Root cause: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command.

10

Hi @karl

1. Appium upgrade - downgrade

To upgrade or downgrade any appium version on Windows, you should follow these steps:

taskill /IM /F adb.exe
taskill /IM /F node.exe
npm uninstall -g appium
npm install -g appium@<desired_version> //replace the desired_version
npm cache clean --force

Manually remove io.appium.uiautomator2.server.test and io.appium.uiautomator2.server from the device

2. The error

Back to your tapAtPosition error, could you please show us the full stack trace?

Thanks.

1 Like
11

@duyluong,

Now it is all good, Katalon 6.2 and Appium 1.12.1.

I performed a manual uninstall of the uiautomator2 with ADB and by the end, I discovered that I had some SDK files corrupted. So. all was sorted with a clean install of Appium 1.12.1 and the Android SDK.

About the TapAtPosition, I am not having more problems since I fixed my side.

Thanks for the support.

1 Like
12

I am getting an error opening the Chrome browser: com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’

The code for opening the browser is WebUI.openBrowser(’’). This works fine in Firefox, but fails with Chrome (on MacOS).

Edit: The steps here fixed the issue: Problem with Google chrome 74

13

As the new chrome driver is not updated with the katalon package…so kindly replace the existing chrome driver.exe file with the new one

14

Hello,

During my debugging for Android and iOS I have been checking the custom code and validating we can step through the code correctly. I noticed the views for debug appear incorrect. When you run the test script in debug you start in Keyword view which has the debug step controls disabled. When a break point is discovered the script stops and is displaying the step in the Keyword view with no variable output. I switched to Debug and the variables are displayed but there are no step controls to walk the code in the method.

I checked on 6.1.1 and this is not the same behavior. on 6.1.1 the step controls are available in the debug view so one can step the code and see the variable values change.

2%20RC1%20Keyword%20view%20during%20debug
2%20RC1%20Keyword%20view%20during%20debug1936×1056 282 KB

Show Keyword view during debug with the step controls
2%20RC1%20Debug%20view%20during%20debug
2%20RC1%20Debug%20view%20during%20debug1936×1056 308 KB

Note Debug is selected, and variables are displayed but the step controls are not available.

Reset the perspective but the same view is displayed.

Thank you,
Paul

15

Hello, having trouble setting up a real device to work with this version.

Trying on a MacBook Pro that was just wiped and reinstalled macOS.
Carthage 0.33.0
iOS-deploy 1.9.4
libimobiledevice 1.2.0_3
usbmuxd 1.0.10_1
iOS-webkit-debug-proxy 1.8.4
npm 6.9.0
node v12.1.0
appium 1.12.1
appium directory set to: /usr/local/lib/node_modules/appium
Xcode 10.2.1
iOS 12.2
Enable UI Automation is enabled in developer settings on real device
MacBook Pro running macOS Mojave 10.14.4
WebDriverAgentLib and Runner build without signing issues
Was able to run WebDriverAgent, command ended with this output
Test Suite ‘All tests’ started at 2019-05-06 15:36:49.601

Test Suite ‘WebDriverAgentRunner.xctest’ started at 2019-05-06 15:36:49.602

Test Suite ‘UITestingUITests’ started at 2019-05-06 15:36:49.602

Test Case ‘-[UITestingUITests testRunner]’ started.

t = 0.00s Start Test at 2019-05-06 15:36:49.603

t = 0.00s Set Up

2019-05-06 15:36:49.607679-0400 WebDriverAgentRunner-Runner[944:435274] Built at May 6 2019 15:33:10

2019-05-06 15:36:49.622418-0400 WebDriverAgentRunner-Runner[944:435274] ServerURLHere->http://192.168.1.73:8100<-ServerURLHere

2019-05-06 15:36:49.622789-0400 WebDriverAgentRunner-Runner[944:435320] Using singleton test manager

I was able to access the WebDriverAgent server status on the real device with curl.

The device is trusted to this computer

Running the command ‘idevice_id -l’ lists the real device in its output.

When I try to spy/run on Katalon, only the simulators are listed and not the real device I have connected.

Tried adding the settings/internal/com.kms.katalon.core.mobile.ios.properties file with the ID of my real device but it still didn’t work. It said device missing. When I switched to the ID of a simulator it worked.

I’ve tried reinstalling the requirements with no luck, also tried reinstalling Xcode and Katalon 6.2. Could anyone please provide any help? I want to start on iOS 12.2 automation as soon as possible.

Thank you for your time!

1 Like
16

Hi @Justin_Keller,

Your setup seems to be correct, but please share us these information and command output to investigate better:

  • The screenshot of Katalon Device List.
  • Command output of:
which idevice_id

echo $PATH$

Thanks.

1 Like
17

Hi @qsbetatest,

We will fix this in v6.2.0 release.

Many thanks for your report.

1 Like
18

Hey, thank you for your reply

image
image1838×1854 436 KB

which idevice_id
/usr/local/bin/idevice_id

echo $PATH$
/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin$

1 Like
19

Also,

The output of idevice_id --list is only the ID of the real device I’m trying to use

20

Hi @Justin_Keller,

The first empty item on the dropdown means Katalon Studio could not retrieve your real device info via command:

idevicepair pair -u <device_id>

The <device_id> is the real device id that you get from idevice_id -l command.

Please show us the command output above.
Thanks.

1 Like
21

Hi @duyluong,

I have all running on windows, but on Mac I am facing the same issue that @Justin_Keller.

I have followed the suggested process and I can see the device with idevice_id -l and I can pair with it using the idevicepair pair -u (SUCCESS: Paired with device …), however, Katalon Studio is only displaying the Simulators and a blank phone entry (the blank entry gives an error saying that there is no device selected):

KAtalon%20Device
KAtalon%20Device804×799 92.5 KB

Any other suggestion? I can also see the device when I run: instruments -s devices.

Thanks in advance.

22

Hi @karl,

Please show me these commands output:

ideviceinfo -u <device_id>
idevicepair pair -u <device_id>
23

Hey @duyluong,

The real device I’m using is an iPhone XR with a UDID in this format:********-****************
25 characters in total, including the dash.

I ran the command with this device’s UDID and got the following output:

image
image1056×586 156 KB

I found a suggestion from this post to try without the UDID (this is the only real device I have connected to the laptop currently): UDID validation needed for iPhone XS - it is no longer 40 digits and has a dash in it · Issue #100 · libimobiledevice/ideviceinstaller · GitHub

And I got the following output:

image
image992×62 30.5 KB

After accepting the dialog I ran again:
image

After these steps I restarted Katalon and unfortunately the first empty item on the dropdown is still there.

SOLUTION

I followed the steps in this post: https://github.com/flutter/flutter/issues/22595

Blockquote
brew update
brew uninstall --ignore-dependencies libimobiledevice
brew uninstall --ignore-dependencies usbmuxd
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice

image
image1242×298 62.2 KB

And it works! Apparently the brew package of usbmuxd, the version recommended in this post, no longer works due to a constraints. Thanks again as this pointed me in the right direction to find a solution and I hope this helps you guys/other users if they have issues as well.

@karl looks like you and I were in the same boat, try this out and let us know!

4 Likes