Katalon run on iOS 12

Archive
,
1

Hi team,

Is katalon support run in iOS 12?
I’m using :

  • Katalon studio 6.0.5
  • Appium 1.8.1
  • iPhone 7 iOS 12.1.4
  • Xcode 10.1

Thank you

2

Hi @Raka_Aditoro_Faturah,

Katalon Studio will support iOS 12 and Xcode 10 if you use Appium 1.8.2-beta:

npm install -g appium@1.8.2-beta

Hope this helps,

Chris

3

Hi Chris,

Thanks for your reply, i will change my appium.

4

Hi Chris,

I’ve try spy mobile with appium 1.8.2-beta but i’m facing this error

07
071040×386 55.5 KB

Could you guide me to resolve this?
And why i have to wait about 8-10 min to get the error? :frowning:
Is there anyway to make it faster?

Thanks you.

5

Hi @Raka_Aditoro_Faturah,

Here’s a few things you could try:

  1. Make sure you don’t have any rogue Appium processes running in the background (see the bottom part of this post): Troubleshooting Exceptions on Mobile - (Appium 1.8.1 is Recommended)

  2. Quit Katalon, the iOS simulators, and your machine - sometimes this can help to free up any processes

  3. Make sure you have the WebDriverAgent project installed and that you can communicate with it: https://docs.katalon.com/katalon-studio/docs/installing-webdriveragent-for-ios-devices.html

Hope this helps,

Chris

6

Hello Chris…
I’m using :

  • Katalon studi 5.10.1
  • appium 1.8.2-beta
  • real device iPhone 7 iOS 12.1.4
  • XCode 10.1

when I run the test case, there is a huge delay between WDA successfully installed to execute the first step. it took approximately 5 minutes for one test case. even though it’s only 3 rows of steps.
Can you help me?
thanks

7

Hi @akbar_rosyidhana,

Does this slow down also happen in a simulator or is it only on real devices?

Is anything going on in the logs or console during the time you’re waiting? Is it just hanging?

Sometimes (especially after you’ve had some test failures) there are rogue appium processes that don’t exit when there are Katalon errors. These can interview with new tests and causes them to be unresponsive. To try to clear these out, the most straightforward way is to quit Katalon, close the simulators, and restart your computer.

Alternatively, you can check to see if there are running appium processes in the Terminal using ps -ef | grep appium. You might see something like this:

  501 48742     1   0 Fri02PM ??         0:04.12 /usr/local/Cellar/node/9.11.1/bin/node /Users/chris/.nvm/versions/node/v9.2.0/lib/node_modules/appium/build/lib/main.js --tmp /var/folders/90/26pjk1q50wd9xfn9q3q6tkyc0000gn/T//Katalon/Appium/Temp1551470186488 -p 55334 --chromedriver-port 55335 --log-level info --webkit-debug-proxy-port 0
  501 60974     1   0 Sat11PM ??         0:40.81 /usr/local/Cellar/node/9.11.1/bin/node /Users/chris/.nvm/versions/node/v9.2.0/lib/node_modules/appium/build/lib/main.js --tmp /var/folders/90/26pjk1q50wd9xfn9q3q6tkyc0000gn/T//Katalon/Appium/Temp1551587426507 -p 51192 --chromedriver-port 51193 --log-level info --webkit-debug-proxy-port 0

In these cases, the 2nd column is the process id, e.g. 48742 and 60974. To kill those processes, you can use kill <processid> in the Terminal where <processid> is the id from the listing. If they don’t seem to close, you can be more forceful with kill -9 <processid>.

Try re-running your tests after the processes have been cleared up.

Hope this helps,

Chris

8

it happened to both. Real device and a simulator.

“Is anything going on in the logs or console during the time you’re waiting? Is it just hanging?” <<< I’m not sure. sometimes just hanging but sometimes give some logs. I’m going to reproduce today. I will update here as soon as I get the log. And I will try your advice first.

9

Hello @Chris_Trevarthen
I’ve tried your advice but still the same. Huge delay still happened.

“Is anything going on in the logs or console during the time you’re waiting? Is it just hanging?” << after reproduce, I’m pretty sure it was just hanging.
Right after this log :

[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}
[WD Proxy] Got an unexpected response: {“errno”:“ECONNRESET”,“code”:“ECONNRESET”,“syscall”:“read”}

Could you help me?
Thanks