How to connect the device by katalon?


#1

image


#2

Hi tester:

Can you give more data context? katalon version, os, appium version, log, perform what action error shows, android or ios?

Please follow this directions.


#3

Hello, here is my log by using mobile record!
e[35m[Appium]e[39m Welcome to Appium v1.14.0
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 43830
e[35m[Appium]e[39m Welcome to Appium v1.14.0
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m chromeDriverPort: 43831
e[35m[Appium]e[39m port: 43830
e[35m[Appium]e[39m tmpDir: C:\Users\54275\AppData\Local\Temp\Katalon\Appium\Temp1564451323815
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:43830
e[35m[Appium]e[39m chromeDriverPort: 43831
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[Appium]e[39m tmpDir: C:\Users\54275\AppData\Local\Temp\Katalon\Appium\Temp1564451323815
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:43830
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[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[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[90m{}e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m1 ms - 68e[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[90m{}e[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[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m1 ms - 68e[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk”,“noReset”:true,“newCommandTimeout”:1800,“platformVersion”:“6.0”,“autoGrantPermissions”:true,“platformName”:“Android”,“udid”:“3CG6T16905010864”,“deviceName”:“HUAWEI NEM-AL10 (Android 6.0)”,“fullReset”:false,“platform”:“ANDROID”},“capabilities”:{“firstMatch”:[{“appium:app”:“C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk”,“appium:autoGrantPermissions”:true,“appium:deviceName”:“HUAWEI NEM-AL10 (Android 6.0)”,“appium:fullReset”:false,“appium:newCommandTimeout”:1800,“appium:noReset”:true,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“6.0”,“appium:udid”:“3CG6T16905010864”}]}}e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[BaseDriver]e[39m The capabilities [“platform”] are not standard capabilities and should have an extension prefix
e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
e[35m[Appium]e[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk”,“noReset”:true,“newCommandTimeout”:1800,“platformVersion”:“6.0”,“autoGrantPermissions”:true,“platformName”:“Android”,“udid”:“3CG6T16905010864”,“deviceName”:“HUAWEI NEM-AL10 (Android 6.0)”,“fullReset”:false,“platform”:“ANDROID”},“capabilities”:{“firstMatch”:[{“appium:app”:“C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk”,“appium:autoGrantPermissions”:true,“appium:deviceName”:“HUAWEI NEM-AL10 (Android 6.0)”,“appium:fullReset”:false,“appium:newCommandTimeout”:1800,“appium:noReset”:true,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“6.0”,“appium:udid”:“3CG6T16905010864”}]}}e[39m
e[35m[Appium]e[39m ======================================================================
e[35m[BaseDriver]e[39m The capabilities [“platform”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m DEPRECATION WARNING:
e[35m[Appium]e[39m
e[35m[Appium]e[39m
e[35m[Appium]e[39m ======================================================================
e[35m[Appium]e[39m The ‘automationName’ capability was not provided in the desired
e[35m[Appium]e[39m DEPRECATION WARNING:
e[35m[Appium]e[39m capabilities for this Android session
e[35m[Appium]e[39m
e[35m[Appium]e[39m
e[35m[Appium]e[39m The ‘automationName’ capability was not provided in the desired
e[35m[Appium]e[39m Setting ‘automationName=UiAutomator2’ by default and using the
e[35m[Appium]e[39m capabilities for this Android session
e[35m[Appium]e[39m UiAutomator2 Driver
e[35m[Appium]e[39m
e[35m[Appium]e[39m
e[35m[Appium]e[39m Setting ‘automationName=UiAutomator2’ by default and using the
e[35m[Appium]e[39m The next major version of Appium (2.x) will require the
e[35m[Appium]e[39m UiAutomator2 Driver
e[35m[Appium]e[39m ‘automationName’ capability to be set for all sessions on all
e[35m[Appium]e[39m
e[35m[Appium]e[39m platforms
e[35m[Appium]e[39m The next major version of Appium (2.x) will require the
e[35m[Appium]e[39m
e[35m[Appium]e[39m ‘automationName’ capability to be set for all sessions on all
e[35m[Appium]e[39m In previous versions (Appium <= 1.13.x), the default was
e[35m[Appium]e[39m platforms
e[35m[Appium]e[39m ‘automationName=UiAutomator1’
e[35m[Appium]e[39m
e[35m[Appium]e[39m
e[35m[Appium]e[39m In previous versions (Appium <= 1.13.x), the default was
e[35m[Appium]e[39m If you wish to use that automation instead of UiAutomator2, please
e[35m[Appium]e[39m ‘automationName=UiAutomator1’
e[35m[Appium]e[39m add ‘automationName=UiAutomator1’ to your desired capabilities
e[35m[Appium]e[39m
e[35m[Appium]e[39m
e[35m[Appium]e[39m If you wish to use that automation instead of UiAutomator2, please
e[35m[Appium]e[39m For more information about drivers, please visit
e[35m[Appium]e[39m add ‘automationName=UiAutomator1’ to your desired capabilities
e[35m[Appium]e[39m http://appium.io/docs/en/about-appium/intro/ and explore the
e[35m[Appium]e[39m
e[35m[Appium]e[39m ‘Drivers’ menu
e[35m[Appium]e[39m For more information about drivers, please visit
e[35m[Appium]e[39m
e[35m[Appium]e[39m http://appium.io/docs/en/about-appium/intro/ and explore the
e[35m[Appium]e[39m ======================================================================
e[35m[Appium]e[39m ‘Drivers’ menu
e[35m[Appium]e[39m
e[35m[Appium]e[39m
e[35m[Appium]e[39m Appium v1.14.0 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m ======================================================================
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m
e[35m[Appium]e[39m platform: ANDROID
e[35m[Appium]e[39m Appium v1.14.0 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m platformName: android
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m app: C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk
e[35m[Appium]e[39m platform: ANDROID
e[35m[Appium]e[39m autoGrantPermissions: true
e[35m[Appium]e[39m platformName: android
e[35m[Appium]e[39m deviceName: HUAWEI NEM-AL10 (Android 6.0)
e[35m[Appium]e[39m app: C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk
e[35m[Appium]e[39m fullReset: false
e[35m[Appium]e[39m autoGrantPermissions: true
e[35m[Appium]e[39m newCommandTimeout: 1800
e[35m[Appium]e[39m deviceName: HUAWEI NEM-AL10 (Android 6.0)
e[35m[Appium]e[39m noReset: true
e[35m[Appium]e[39m fullReset: false
e[35m[Appium]e[39m platformVersion: 6.0
e[35m[Appium]e[39m newCommandTimeout: 1800
e[35m[Appium]e[39m udid: 3CG6T16905010864
e[35m[Appium]e[39m noReset: true
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
e[35m[Appium]e[39m platformVersion: 6.0
e[35m[BaseDriver]e[39m platform
e[35m[Appium]e[39m udid: 3CG6T16905010864
e[35m[BaseDriver]e[39m Session created with session id: 97f29fcc-2776-4576-8a0c-74e8c5ee22f8
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
e[35m[BaseDriver]e[39m Using local app ‘C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk’
e[35m[BaseDriver]e[39m platform
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\54275.katalon\tools\android_sdk’ (newest first):
e[35m[BaseDriver]e[39m Session created with session id: 97f29fcc-2776-4576-8a0c-74e8c5ee22f8
e[35m[ADB]e[39m C:/Users/54275/.katalon/tools/android_sdk/build-tools/29.0.0
e[35m[BaseDriver]e[39m Using local app ‘C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk’
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\54275.katalon\tools\android_sdk’ (newest first):
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[ADB]e[39m C:/Users/54275/.katalon/tools/android_sdk/build-tools/29.0.0
e[35m[AndroidDriver]e[39m Using device: 3CG6T16905010864
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\54275\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\build-tools\29.0.0\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\54275.katalon\tools\android_sdk’?
e[35m[AndroidDriver]e[39m Using device: 3CG6T16905010864
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\aapt.exe’
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[ADB]e[39m Extracting package and launch activity from manifest
e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\54275\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\build-tools\29.0.0\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\54275.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Package name: ‘com.yunda.ydqiantong’
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\aapt.exe’
e[35m[ADB]e[39m Main activity name: ‘com.yunda.ydqiantong.function.login.activity.QTSplashActivity’
e[35m[ADB]e[39m Extracting package and launch activity from manifest
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat’
e[35m[ADB]e[39m Package name: ‘com.yunda.ydqiantong’
e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\zipalign.exe’
e[35m[ADB]e[39m Main activity name: ‘com.yunda.ydqiantong.function.login.activity.QTSplashActivity’
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat’
e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\zipalign.exe’
e[35m[UiAutomator2]e[39m Server packages are going to be (re)installed
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[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 io.appium.uiautomator2.server was successfully uninstalled
e[35m[ADB]e[39m The application at ‘C:\Users\54275\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/fe3aa6662b6c999cf661d7626a50da395fd786f4.apk’
e[35m[ADB]e[39m The application at ‘C:\Users\54275\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/fe3aa6662b6c999cf661d7626a50da395fd786f4.apk’
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v3.7.0.apk’ took 6.319s
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v3.7.0.apk’ took 6.319s
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
e[35m[ADB]e[39m The application at ‘C:\Users\54275\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/cad8c04fbd5464da6bcfc8fe6ec84d3f914941ca.apk’
e[35m[ADB]e[39m The application at ‘C:\Users\54275\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/cad8c04fbd5464da6bcfc8fe6ec84d3f914941ca.apk’
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 2.896s
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 2.896s
e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 3.7.0
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\54275\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ and test from ‘C:\Users\54275\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…
e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 3.7.0
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\54275\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ and test from ‘C:\Users\54275\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…
e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
e[35m[ADB]e[39m No ‘uiautomator’ process has been found
e[35m[ADB]e[39m No ‘uiautomator’ process has been found
image


#4

Hi tester:

Add these configuration on desired capabilities on and try again.

Project -> Settings -> Desired capabilities -> Mobile -> Android.

I hope this help you. I’m not an expert on Katalon but i have similar issues to record with some apps.

finally you need enabled
In the Developer Options on your mobile user interface, enable:

  • USB debugging – Debug mode when USB is connected
  • Install via USB – Allow installing apps via USB
  • USB debugging (Security Setting) – Allow granting permissions and simulating input via USB debugging.

#5

Sorry,it is unable.
e[35m[Appium]e[39m Welcome to Appium v1.14.0
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 29159
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 29160
e[35m[Appium]e[39m tmpDir: C:\Users\54275\AppData\Local\Temp\Katalon\Appium\Temp1564535987445
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:29159
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[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[90m1 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”:“C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk”,“noReset”:true,“appWaitActivity”:".function.login.activity.QTSplashActivity",“appWaitPackage”:“com.yunda.ydqiantong”,“deviceId”:"",“deviceName”:“HUAWEI NEM-AL10 (Android 6.0)”,“fullReset”:false,“platform”:“ANDROID”,“newCommandTimeout”:1800,“platformVersion”:“6.0”,“autoGrantPermissions”:true,“platformName”:“Android”,“udid”:“3CG6T16905010864”},“capabilities”:{“firstMatch”:[{“appium:app”:“C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk”,“appium:appWaitActivity”:".function.login.activity.QTSplashActivity",“appium:appWaitPackage”:“com.yunda.ydqiantong”,“appium:autoGrantPermissions”:true,“deviceId”:"",“appium:deviceName”:“HUAWEI NEM-AL10 (Android 6.0)”,“appium:fullReset”:false,“appium:newCommandTimeout”:1800,“appium:noReset”:true,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“6.0”,“appium:udid”:“3CG6T16905010864”}]}}e[39m
e[35m[BaseDriver]e[39m The capabilities [“deviceId”,“platform”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m
e[35m[Appium]e[39m ======================================================================
e[35m[Appium]e[39m DEPRECATION WARNING:
e[35m[Appium]e[39m
e[35m[Appium]e[39m The ‘automationName’ capability was not provided in the desired
e[35m[Appium]e[39m capabilities for this Android session
e[35m[Appium]e[39m
e[35m[Appium]e[39m Setting ‘automationName=UiAutomator2’ by default and using the
e[35m[Appium]e[39m UiAutomator2 Driver
e[35m[Appium]e[39m
e[35m[Appium]e[39m The next major version of Appium (2.x) will require the
e[35m[Appium]e[39m ‘automationName’ capability to be set for all sessions on all
e[35m[Appium]e[39m platforms
e[35m[Appium]e[39m
e[35m[Appium]e[39m In previous versions (Appium <= 1.13.x), the default was
e[35m[Appium]e[39m ‘automationName=UiAutomator1’
e[35m[Appium]e[39m
e[35m[Appium]e[39m If you wish to use that automation instead of UiAutomator2, please
e[35m[Appium]e[39m add ‘automationName=UiAutomator1’ to your desired capabilities
e[35m[Appium]e[39m
e[35m[Appium]e[39m For more information about drivers, please visit
e[35m[Appium]e[39m http://appium.io/docs/en/about-appium/intro/ and explore the
e[35m[Appium]e[39m ‘Drivers’ menu
e[35m[Appium]e[39m
e[35m[Appium]e[39m ======================================================================
e[35m[Appium]e[39m
e[35m[Appium]e[39m Appium v1.14.0 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m Capabilities:
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 app: C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk
e[35m[Appium]e[39m appWaitActivity: .function.login.activity.QTSplashActivity
e[35m[Appium]e[39m appWaitPackage: com.yunda.ydqiantong
e[35m[Appium]e[39m autoGrantPermissions: true
e[35m[Appium]e[39m deviceName: HUAWEI NEM-AL10 (Android 6.0)
e[35m[Appium]e[39m fullReset: false
e[35m[Appium]e[39m newCommandTimeout: 1800
e[35m[Appium]e[39m noReset: true
e[35m[Appium]e[39m platformVersion: 6.0
e[35m[Appium]e[39m udid: 3CG6T16905010864
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 Session created with session id: 7a47158a-02a3-44cc-a91c-0043bfeb8ebe
e[35m[BaseDriver]e[39m Using local app ‘C:\Users\54275\Desktop\katalon\android demo.prj\V2.0.0.01.apk’
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\54275.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/54275/.katalon/tools/android_sdk/build-tools/29.0.0
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: 3CG6T16905010864
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\54275\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\54275\.katalon\tools\android_sdk\build-tools\29.0.0\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\54275.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\54275.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.yunda.ydqiantong’
e[35m[ADB]e[39m Main activity name: ‘com.yunda.ydqiantong.function.login.activity.QTSplashActivity’
e[35m[AndroidDriver]e[39m Granting android.permission.SET_ANIMATION_SCALE, CHANGE_CONFIGURATION, ACCESS_FINE_LOCATION by pm grant
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat’
e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\54275.katalon\tools\android_sdk\build-tools\29.0.0\zipalign.exe’
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 The application at ‘C:\Users\54275\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/fe3aa6662b6c999cf661d7626a50da395fd786f4.apk’
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v3.7.0.apk’ took 7.111s
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
e[35m[ADB]e[39m The application at ‘C:\Users\54275\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/cad8c04fbd5464da6bcfc8fe6ec84d3f914941ca.apk’
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 2.656s
e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 3.7.0
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\54275\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ and test from ‘C:\Users\54275\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…
e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
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…
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


#6

Hi tester

Please set appWaitActivity: *
Not appWaitActivity: .function.login.activity.QTSplashActivity.
I suggest update katalon studio and get the latest version of android sdk.
I you can test in a emulated device to quit the variable of physical device configuration problem.
Can you attach the apk to test in my machine?
I can’t imagine doing more than that.


#7

@tester20183450
Did you solve your problem?
How do you solve?
Please share your solution to help other with the same problem.

Thanks