Unable to do mobile record function

[lwz]

Hi, I’m a new user to Katalon (also novice to computing related stuff) and I’ve been trying out the mobile recorder function to test a mobile application. I’m not sure if this is a common problem due to my negligence, but I’m unable to solve this problem for awhile already. Hoping to get some answers here

After following the steps to install respective softwares I proceeded to try out on the mobile recorder function, hoping to record my first mobile app test case. However, I encountered this long error message.

Below are the steps I took before trying to create the test case.

1. Install node.js and appium, ensuring java is installed
   

   

2. Enabled developer option in my Samsung S8 phone, with USB debugging enabled as well.
   Connected phone to laptop.

3. Start Katalon, create new project
   

   

4. Create new test case, click “Record mobile”, browsed to the .apk file in my phone and computer. Clicked on “start”
   

   

5. Following error message (same as the one I have shown at the start) appeared.
   

   

Pardon me if I missed any steps due to negligence, or if the problem is too basic, but I have tried searching for a solution for awhile already but to no avail. Really hoping I will get some answers here.

Thanks in advance to whoever’s helping me. Cheers!

[duyluong]

Hi @lwz,

Appium shows that it cannot access or extract the apk file or access to folder C:\Users\Wei Zhong\App Data\Local\Microsoft\Windows\INetCache\HB1UG7F0.

Please make sure the folder above can access by the current user or run Katalon Studio by Administrator.

Thanks

[lwz]

Hi, really thanks for the prompt reply!
I did what you said, but a new error message surfaced.

I can’t seem to find where can I increase the “adb execution” as stated. Sorry for the trouble.

[duyluong]

@lwz,

The above suggestion seems to resolve the first issue. The second error shows adb could not install apk on your devices.
Please set capability:
uiautomator2ServerInstallTimeout: 60000 (milliseconds) in Project Settings/Desired Capabilities/Android like the screenshot below:

When adb starts installing apk on your device, please remember to accept the installation confirmation.

Thanks

[lwz]

Hi thank you for the reply. Currently the issue went back to the error of having no write access. Running Katalon as administrator doesn’t work, and I can’t seem to grant the write permissions because an error message keeps popping up, saying that I need the admin access, no matter how I enable it. Are you able to help? I’m sorry that this issue is turning into a windows problem…

[lwz]

Hi! I don’t have that error message anymore, I have no idea what I did either but there’s a new error message now. I’m not quite sure whether this error comes before or after the first error I have shown, but here it is. “The instrumentation process cannot be initialized…”

Below is the part of the message when the recorder is attempting to open the app:

e[35m[Appium]e[39m Welcome to Appium v1.13.0
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 57926
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 57927
e[35m[Appium]e[39m tmpDir: C:\Users\WEIZHO~1\AppData\Local\Temp\Katalon\Appium\Temp1564023781282
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:57926
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[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\Wei Zhong\Desktop\DynamicWeb\Katalon\Testing on TWG mobile app\androidapp\twgtea.TWGTEA-Signed.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceId”:“”,“deviceName”:“samsung SM-G950F (Android 8.0.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“ce051715746f204c0d”,“uiautomator2ServerInstallTimeout”:60000},“capabilities”:{“desiredCapabilities”:{“app”:“C:\Users\Wei Zhong\Desktop\DynamicWeb\Katalon\Testing on TWG mobile app\androidapp\twgtea.TWGTEA-Signed.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceId”:“”,“deviceName”:“samsung SM-G950F (Android 8.0.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“ce051715746f204c0d”,“uiautomator2ServerInstallTimeout”:60000},“firstMatch”:[{“platformName”:“android”}]}}e[39m
e[35m[Appium]e[39m Could not parse W3C capabilities: ‘deviceName’ can’t be blank
e[35m[Appium]e[39m Trying to fix W3C capabilities by merging them with JSONWP caps
e[35m[BaseDriver]e[39m The capabilities [“app”,“autoGrantPermissions”,“automationName”,“deviceId”,“deviceName”,“fullReset”,“newCommandTimeout”,“noReset”,“platform”,“udid”,“uiautomator2ServerInstallTimeout”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m Appium v1.13.0 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m app: C:\Users\Wei Zhong\Desktop\DynamicWeb\Katalon\Testing on TWG mobile app\androidapp\twgtea.TWGTEA-Signed.apk
e[35m[Appium]e[39m autoGrantPermissions: true
e[35m[Appium]e[39m automationName: uiautomator2
e[35m[Appium]e[39m deviceId:
e[35m[Appium]e[39m deviceName: samsung SM-G950F (Android 8.0.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 platform: ANDROID
e[35m[Appium]e[39m udid: ce051715746f204c0d
e[35m[Appium]e[39m uiautomator2ServerInstallTimeout: 60000
e[35m[Appium]e[39m platformName: android
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: bc1a8384-7179-4161-a5df-1b047c2fc4ca
e[35m[BaseDriver]e[39m Using local app ‘C:\Users\Wei Zhong\Desktop\DynamicWeb\Katalon\Testing on TWG mobile app\androidapp\twgtea.TWGTEA-Signed.apk’
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\Wei Zhong.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/Wei Zhong/.katalon/tools/android_sdk/build-tools/29.0.0
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\Wei Zhong.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: ce051715746f204c0d
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\Wei Zhong.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\Wei Zhong\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\Wei Zhong\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\Wei Zhong\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\Wei Zhong\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\Wei Zhong\.katalon\tools\android_sdk\build-tools\29.0.0\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\Wei Zhong.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\Wei Zhong.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: ‘twgtea.TWGTEA’
e[35m[ADB]e[39m Main activity name: ‘md534aad4f5011cac53a06fe8c536b16b15.SplashScreen’
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\Wei Zhong.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat’
e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\Wei Zhong.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\Wei Zhong\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.5.1.apk’ is already cached to ‘/data/local/tmp/appium_cache/56abf1bf10f6562619a2dd8fb060718e27c4cb28.apk’
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v3.5.1.apk’ took 16.884s
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
e[35m[ADB]e[39m The application at ‘C:\Users\Wei Zhong\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/c6e9cdfe0da1784c2c695fae7c66184003868a40.apk’
e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 16.354s
e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 3.5.1
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\Wei Zhong\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.5.1.apk’ and test from ‘C:\Users\Wei Zhong\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…

I know it’s a lot but I really appreciate your help! Thanks!

[duyluong]

Please add this property in Desired Capbilities/Mobile/Android:

appWaitActivity: *

Thanks