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

Hi @qsbetatest,

We will fix this in v6.2.0 release.

Many thanks for your report.

1 Like

Hey, thank you for your reply


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

Also,

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

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

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

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

Thanks in advance.

Hi @karl,

Please show me these commands output:

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

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:

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:

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

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

Hi,

ideviceinfo : ERROR could not connect to lockdownd error code -21
idevicepair : SUCCESS: Paired with device xxxx

Investigating this error I followed this post:

Now Katalon Studio is showing the device.

@duyluong thanks again for the help, appreciate it!

2 Likes

Looks like we came across just about the same solution lol

2 Likes

Hi @duyluong,

I’m encountering the same problem as karl and Paul did. I was initially on Appium 1.8.2 and things were working fine. However when upgrading to 1.12.1, I ran into the same error as above. I tried your steps for upgrading but still have the same error. I’m also on Katalon 6.2.0.rc1.

Using Windows 10.

Devices used:
Samsung S8 - Android 8.0
Sony Xperia XZ Premium - Pie 9.0

I have also made sure to manually remove io.appium.uiautomator2.server.test and appium.uiautomator2.server from the devices, but still the error appears. Am I missing something?

Thanks,
Raul

Hi @raul,

If you upgrade appium from v1.8.1 to v1.12.1. Please follow these manual instruction:

  • Manually remove io.appium.uiautomator2.server.test and appium.uiautomator2.server from your devices.
  • Manually delete folder C://<user_folder>/.katalon/tools/android_sdk and let Katalon download again.

Thanks

1 Like

Hi @duyluong,

I followed the additional steps you gave me, but the same error is still occurring. In addition to the same error above, I have also attached additional logs, hopefully, to aid in troubleshooting.

SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
2019-06-12 10:47:35.469 INFO  c.k.katalon.core.main.TestCaseExecutor   - --------------------
2019-06-12 10:47:35.472 INFO  c.k.katalon.core.main.TestCaseExecutor   - START Test Cases/reuse/Login
2019-06-12 10:47:35.919 DEBUG testcase.Login                           - 1: startApplication("D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk", true)
2019-06-12 10:47:36.166 INFO  c.k.k.c.m.k.i.MobileDriverFactory        - User set preference: ['appWaitActivity', '*']
2019-06-12 10:47:36.167 INFO  c.k.k.c.m.k.i.MobileDriverFactory        - User set preference: ['deviceId', '9887fc474659515641']
e[35m[Appium]e[39m Welcome to Appium v1.12.1
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m   port: 51014
e[35m[Appium]e[39m   chromeDriverPort: 51015
e[35m[Appium]e[39m   tmpDir: C:\Users\iarve\AppData\Local\Temp\\Katalon\Appium\Temp1560350856181
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:51014
2019-06-12 10:47:38.936 INFO  c.k.k.c.a.driver.AppiumDriverManager     - Appium server started on port 51,014
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
[debug] e[35m[GENERIC]e[39m Calling AppiumDriver.getStatus() with args: []
[debug] e[35m[GENERIC]e[39m Responding to client with driver.getStatus() result: {"build":{"version":"1.12.1"}}
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m6 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":{"app":"D:\\Work Stuff\\automation-new\\arvee\\mobile-android\\Data Files\\nf312.apk","noReset":false,"appWaitActivity":"*","deviceId":"9887fc474659515641","deviceName":"samsung SM-G950U (Android 8.0.0)","fullReset":true,"platform":"ANDROID","newCommandTimeout":1800,"platformVersion":"8.0.0","automationName":"uiautomator2","autoGrantPermissions":true,"platformName":"Android","udid":"9887fc474659515641"},"capabilities":{"firstMatch":[{"appium:app":"D:\\Work Stuff\\automation-new\\arvee\\mobile-android\\Data Files\\nf312.apk","appium:appWaitActivity":"*","appium:autoGrantPermissions":true,"appium:automationName":"uiautomator2","deviceId":"9887fc474659515641","appium:deviceName":"samsung SM-G950U (Android 8.0.0)","appium:fullReset":true,"appium:newCommandTimeout":1800,"appium:noReset":false,"platform":"ANDROID","platformName":"android","appium:platformVersion":"8.0.0","appium:udid":"9887fc474659515641"}]}}e[39m
[debug] e[35m[W3C]e[39m Calling AppiumDriver.createSession() with args: [{"app":"D:\\Work Stuff\\automation-new\\arvee\\mobile-android\\Data Files\\nf312.apk","noReset":false,"appWaitActivity":"*","deviceId":"9887fc474659515641","deviceName":"samsung SM-G950U (Android 8.0.0)","fullReset":true,"platform":"ANDROID","newCommandTimeout":1800,"platformVersion":"8.0.0","automationName":"uiautomator2","autoGrantPermissions":true,"platformName":"Android","udid":"9887fc474659515641"},null,{"firstMatch":[{"appium:app":"D:\\Work Stuff\\automation-new\\arvee\\mobile-android\\Data Files\\nf312.apk","appium:appWaitActivity":"*","appium:autoGrantPermissions":true,"appium:automationName":"uiautomator2","deviceId":"9887fc474659515641","appium:deviceName":"samsung SM-G950U (Android 8.0.0)","appium:fullReset":true,"appium:newCommandTimeout":1800,"appium:noReset":false,"platform":"ANDROID","platformName":"android","appium:platformVersion":"8.0.0","appium:udid":"9887fc474659515641"}]}]
[debug] e[35m[BaseDriver]e[39m Event 'newSessionRequested' logged at 1560350859773 (10:47:39 GMT-0400 (Eastern Daylight Time))
e[35m[BaseDriver]e[39m The capabilities ["deviceId","platform"] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m Appium v1.12.1 creating new AndroidUiautomator2Driver (v1.33.0) session
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m   deviceId: 9887fc474659515641
e[35m[Appium]e[39m   platform: ANDROID
e[35m[Appium]e[39m   platformName: android
e[35m[Appium]e[39m   app: D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk
e[35m[Appium]e[39m   appWaitActivity: *
e[35m[Appium]e[39m   autoGrantPermissions: true
e[35m[Appium]e[39m   automationName: uiautomator2
e[35m[Appium]e[39m   deviceName: samsung SM-G950U (Android 8.0.0)
e[35m[Appium]e[39m   fullReset: true
e[35m[Appium]e[39m   newCommandTimeout: 1800
e[35m[Appium]e[39m   noReset: false
e[35m[Appium]e[39m   platformVersion: 8.0.0
e[35m[Appium]e[39m   udid: 9887fc474659515641
[debug] e[35m[BaseDriver]e[39m W3C capabilities {"alwaysMatch":{"appium:dev... and MJSONWP desired capabilities {"app":"D:\\Work Stuff\\aut... were provided
[debug] e[35m[BaseDriver]e[39m Creating session with W3C capabilities: {"alwaysMatch":{"appium:dev...
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: deviceId, platform.
e[35m[BaseDriver]e[39m Session created with session id: d655c287-4659-4ec7-b47d-07fc7e878b58
e[35m[BaseDriver]e[39m Using local app 'D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk'
[debug] e[35m[UiAutomator2]e[39m Checking whether app is actually present
e[35m[ADB]e[39m Checking whether adb is present
e[35m[ADB]e[39m Found 1 'build-tools' folders under 'C:\Users\iarve\.katalon\tools\android_sdk' (newest first):
e[35m[ADB]e[39m     C:/Users/iarve/.katalon/tools/android_sdk/build-tools/29.0.0
e[35m[ADB]e[39m Using adb.exe from C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe
e[35m[AndroidDriver]e[39m Retrieving device list
[debug] e[35m[ADB]e[39m Trying to find a connected android device
[debug] e[35m[ADB]e[39m Getting connected devices...
[debug] e[35m[ADB]e[39m 1 device(s) connected
e[35m[AndroidDriver]e[39m Using device: 9887fc474659515641
[debug] e[35m[ADB]e[39m Setting device id to 9887fc474659515641
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell getprop ro.build.version.sdk'
[debug] e[35m[ADB]e[39m Current device property 'ro.build.version.sdk': 26
[debug] e[35m[ADB]e[39m Device API level: 26
[debug] e[35m[AndroidDriver]e[39m Parsing package and activity from app manifest
e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find apkanalyzer.bat in C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat,C:\Users\iarve\.katalon\tools\android_sdk\emulator\apkanalyzer.bat,C:\Users\iarve\.katalon\tools\android_sdk\tools\apkanalyzer.bat,C:\Users\iarve\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat,C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apkanalyzer.bat. Do you have the Android SDK installed at 'C:\Users\iarve\.katalon\tools\android_sdk'?
e[35m[ADB]e[39m Checking whether aapt is present
e[35m[ADB]e[39m Using aapt.exe from C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\aapt.exe
e[35m[ADB]e[39m Extracting package and launch activity from manifest
e[35m[ADB]e[39m Package name: 'com.neuroflow'
e[35m[ADB]e[39m Main activity name: 'com.neuroflow.activities.SplashActivity'
[debug] e[35m[AndroidDriver]e[39m Parsed package and activity are: com.neuroflow/com.neuroflow.activities.SplashActivity
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 wait-for-device'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell echo ping'
[debug] e[35m[AndroidDriver]e[39m Pushing settings apk to device...
[debug] e[35m[ADB]e[39m Getting install status for io.appium.settings
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.settings'
[debug] e[35m[ADB]e[39m 'io.appium.settings' is installed
[debug] e[35m[ADB]e[39m Getting package info for 'io.appium.settings'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.settings'
[debug] e[35m[ADB]e[39m The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('2.14.0' >= '2.14.0')
[debug] e[35m[ADB]e[39m There is no need to install/upgrade 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk'
[debug] e[35m[ADB]e[39m Getting IDs of all 'io.appium.settings' processes
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell 'pgrep --help; echo $?''
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell pgrep \^appium\\.settings\$'
[debug] e[35m[AndroidDriver]e[39m io.appium.settings is already running. There is no need to reset its permissions.
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell appops set io.appium.settings android\:mock_location allow'
[debug] e[35m[Logcat]e[39m Starting logcat capture
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.uiautomator2.server'
[debug] e[35m[ADB]e[39m 'io.appium.uiautomator2.server' is installed
[debug] e[35m[ADB]e[39m Getting package info for 'io.appium.uiautomator2.server'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.uiautomator2.server'
[debug] e[35m[ADB]e[39m The version name of the installed 'io.appium.uiautomator2.server' is greater or equal to the application version name ('3.4.0' >= '3.4.0')
[debug] e[35m[UiAutomator2]e[39m io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.4.0.apk
e[35m[ADB]e[39m Using apksigner.bat from C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat
[debug] e[35m[ADB]e[39m Starting 'C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat' with args '["verify","--print-certs","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-v3.4.0.apk"]'
[debug] e[35m[ADB]e[39m 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.4.0.apk' is signed with non-default certificate
e[35m[ADB]e[39m Checking whether zipalign is present
e[35m[ADB]e[39m Using zipalign.exe from C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\zipalign.exe
[debug] e[35m[ADB]e[39m C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.4.0.apk' is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.4.0.apk' with default cert
[debug] e[35m[ADB]e[39m Starting 'C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat' with args '["sign","--key","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.pk8","--cert","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.x509.pem","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-v3.4.0.apk"]'
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.uiautomator2.server.test'
[debug] e[35m[ADB]e[39m 'io.appium.uiautomator2.server.test' is installed
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[debug] e[35m[ADB]e[39m Starting 'C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat' with args '["verify","--print-certs","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-debug-androidTest.apk"]'
[debug] e[35m[ADB]e[39m 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is signed with non-default certificate
[debug] e[35m[ADB]e[39m C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' with default cert
[debug] e[35m[ADB]e[39m Starting 'C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat' with args '["sign","--key","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.pk8","--cert","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.x509.pem","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-debug-androidTest.apk"]'
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
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.uiautomator2.server'
[debug] e[35m[ADB]e[39m 'io.appium.uiautomator2.server' is installed
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell am force-stop io.appium.uiautomator2.server'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 uninstall io.appium.uiautomator2.server'
[debug] e[35m[ADB]e[39m 'adb uninstall io.appium.uiautomator2.server' command output: Success
e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell ls -t -1 /data/local/tmp/appium_cache'
[debug] e[35m[ADB]e[39m The count of applications in the cache: 11
e[35m[ADB]e[39m The application at 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.4.0.apk' is already cached to '/data/local/tmp/appium_cache/02df6e49ef686c7e87be1bd47bd76ba13524fb68.apk'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell pm install /data/local/tmp/appium_cache/02df6e49ef686c7e87be1bd47bd76ba13524fb68.apk'
e[35m[ADB]e[39m The installation of 'appium-uiautomator2-server-v3.4.0.apk' took 2.072s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package io.appium.uiautomator2.server.test'
[debug] e[35m[ADB]e[39m 'io.appium.uiautomator2.server.test' is installed
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell am force-stop io.appium.uiautomator2.server.test'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 uninstall io.appium.uiautomator2.server.test'
[debug] e[35m[ADB]e[39m 'adb uninstall io.appium.uiautomator2.server.test' command output: Success
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell ls -t -1 /data/local/tmp/appium_cache'
[debug] e[35m[ADB]e[39m The count of applications in the cache: 11
e[35m[ADB]e[39m The application at 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is already cached to '/data/local/tmp/appium_cache/bb1600755ad247966dde9f7a6040be8800e1b123.apk'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell pm install /data/local/tmp/appium_cache/bb1600755ad247966dde9f7a6040be8800e1b123.apk'
e[35m[ADB]e[39m The installation of 'appium-uiautomator2-server-debug-androidTest.apk' took 1.815s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for services to be available
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell pm list instrumentation'
[debug] e[35m[UiAutomator2]e[39m Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[debug] e[35m[UiAutomator2]e[39m Forwarding UiAutomator2 Server port 6790 to 8200
[debug] e[35m[ADB]e[39m Forwarding system: 8200 to device: 6790
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 forward tcp\:8200 tcp\:6790'
[debug] e[35m[ADB]e[39m Uninstalling com.neuroflow
[debug] e[35m[ADB]e[39m Getting install status for com.neuroflow
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package com.neuroflow'
[debug] e[35m[ADB]e[39m 'com.neuroflow' is not installed
e[35m[ADB]e[39m com.neuroflow was not uninstalled, because it was not present on the device
[debug] e[35m[ADB]e[39m Checking app cert for D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk
[debug] e[35m[ADB]e[39m Starting 'C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat' with args '["verify","--print-certs","D:\\Work Stuff\\automation-new\\arvee\\mobile-android\\Data Files\\nf312.apk"]'
[debug] e[35m[ADB]e[39m 'D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk' is signed with non-default certificate
[debug] e[35m[ADB]e[39m D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk' is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing 'D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk' with default cert
[debug] e[35m[ADB]e[39m Starting 'C:\Users\iarve\.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat' with args '["sign","--key","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.pk8","--cert","C:\\Users\\iarve\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.x509.pem","D:\\Work Stuff\\automation-new\\arvee\\mobile-android\\Data Files\\nf312.apk"]'
[debug] e[35m[ADB]e[39m Getting install status for com.neuroflow
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell dumpsys package com.neuroflow'
[debug] e[35m[ADB]e[39m 'com.neuroflow' is not installed
[debug] e[35m[AndroidDriver]e[39m Running full reset on 'com.neuroflow' (reinstall)
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell ls -t -1 /data/local/tmp/appium_cache'
[debug] e[35m[ADB]e[39m The count of applications in the cache: 11
e[35m[ADB]e[39m The application at 'D:\Work Stuff\automation-new\arvee\mobile-android\Data Files\nf312.apk' is already cached to '/data/local/tmp/appium_cache/b3c3518d187117a038fa8c4e277381179d144151.apk'
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell pm install -r -g /data/local/tmp/appium_cache/b3c3518d187117a038fa8c4e277381179d144151.apk'
e[35m[ADB]e[39m The installation of 'nf312.apk' took 3.907s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[UiAutomator2]e[39m Performing shallow cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell am force-stop io.appium.uiautomator2.server.test'
e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 3.4.0
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from 'C:\Users\iarve\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.4.0.apk' and test from 'C:\Users\iarve\AppData\Roaming\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...
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s","9887fc474659515641","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=5807, uid=5807 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server

[debug] e[35m[Instrumentation]e[39m 	at android.os.Parcel.readException(Parcel.java:1967)

[debug] e[35m[Instrumentation]e[39m 	at android.os.Parcel.readException(Parcel.java:1913)

[debug] e[35m[Instrumentation]e[39m 	at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5594)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Instrument.run(Instrument.java:408)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Am.runInstrument(Am.java:232)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Am.onRun(Am.java:125)

[debug] e[35m[Instrumentation]e[39m 	at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Am.main(Am.java:95)

[debug] e[35m[Instrumentation]e[39m 	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService

[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=5807, uid=5807 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server

[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:286)
[debug] e[35m[Instrumentation]e[39m The process has exited with code 1
e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
[debug] e[35m[UiAutomator2]e[39m Performing strict cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell am force-stop io.appium.uiautomator2.server.test'
[debug] e[35m[ADB]e[39m Attempting to kill all uiautomator processes
[debug] e[35m[ADB]e[39m Getting IDs of all 'uiautomator' processes
[debug] e[35m[ADB]e[39m Running 'C:\Users\iarve\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 9887fc474659515641 shell pgrep \^uiautomator\$'
e[35m[ADB]e[39m No 'uiautomator' process has been found
e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online...
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s","9887fc474659515641","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=6150, uid=6150 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server

[debug] e[35m[Instrumentation]e[39m 	at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)

[debug] e[35m[Instrumentation]e[39m 	at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5594)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Instrument.run(Instrument.java:408)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Am.runInstrument(Am.java:232)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Am.onRun(Am.java:125)

[debug] e[35m[Instrumentation]e[39m 	at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)

[debug] e[35m[Instrumentation]e[39m 	at com.android.commands.am.Am.main(Am.java:95)

[debug] e[35m[Instrumentation]e[39m 	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)

[debug] e[35m[Instrumentation]e[39m 	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:286)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService

[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=6150, uid=6150 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server

[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m The process has exited with code 1
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 session
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 server session
[debug] e[35m[WD Proxy]e[39m Matched '/' to command name 'deleteSession'
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

Hi @duyluong

I followed all the steps above mentioned for mac. Everything seems to working fine.

In the end when i am trying to record the mobile app , I am facing the below issue. Sorry I had to attach a picture , couldn’t find a way to copy the pop-up contents. please guide me to overcome this issue.

Hi
I followed the instructions but I got so many semantic issues. Can you please advise how to solve it?

hi @Justin_Keller @duyluong

I have experienced the same issue as yours. the process stuck at the Using singleton test manager and cannot go to the success message listening the USB

Xcode:10.3
Appium: 1.12.1
Katalon: 6.2.0

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

Can you please advise more detailed solution? My physical phone can connect to Katalon and Xcode.

Hi @ppppacchan,

You don’t need to run this test. If you build WebDriverAgentRunner and WebDriverAgentLib success, your XCode settings are done here.

Hi @duyluong
I did try to run a real test case on Katalon without success of running this test. with many efforts, The error returns the same message: An unknown server-side…

Therefore, I guess it was the incorrect configuration for WebDriverAgent.

Can you please have a look at this

Hi @ppppacchan,

XCode 10.x is supported in Katalon Studio v6.2.0 or later. Please update your Katalon Studio.

Thanks

Hi @Justin_Keller, @karl, @duyluong

Thanks for your step.
I have done all the step, but unable to use brew install --HEAD as my MacOS is 10 and xcode is 10

After I install the respective/supported version, still not working
My physical iphone 6 is detected as by KATALON
my local component:
Appium: 1.17.0
Mac OS: 10.14.6
Xcode: 10.1
Carthage: 0.34
iOS-deploy: 1.10
iOS-webkit-debug-proxy: 1.8
Libimobiledevice: 1.8.6
usbmuxd: 2.0.1