Unable to run/start test script in Katalon using iOS webUI using appium 2.0.0-beta.48

Product Forums Katalon Studio
,
1

Hi,
I am unable to start execution run with Katalon. (Cannot also start the Mobile Object Spy)
-Appium: 2.0.0-beta.48
-Xcode - 14.2
-Mac book Pro 14.1
Chip: Apple M1 Pro
MacOS: Ventura 13.1

This is the appium log:
e[35m[Appium]e[39m Welcome to Appium v1.22.3
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 64208
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m tmpDir: /var/folders/6l/k0p5shyx1sqft6k3d0vc4lnm0000gp/T//Katalon/Appium/Temp1672738550858
e[35m[Appium]e[39m chromedriverPort: 64210
e[35m[Appium]e[39m Deprecated server args:
e[35m[Appium]e[39m e[31m–chromedriver-porte[39m => --default-capabilities
e[35m[Appium]e[39m Default capabilities, which will be added to each request unless overridden by desired capabilities:
e[35m[Appium]e[39m chromedriverPort: 64210
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:64208
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[90m3 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”:{“noReset”:false,“bundleId”:“com.apple.mobilesafari”,“deviceId”:“”,“deviceName”:“Btp i7”,“wdaLocalPort”:64223,“webKitDebugProxyPort”:“4723”,“newCommandTimeout”:1800,“realDeviceLogger”:“/Applications/Katalon Studio.app/Contents/Eclipse/configuration/resources/tools/deviceconsole”,“platformVersion”:“15.5”,“automationName”:“XCUITest”,“waitForAppScript”:“true;”,“platformName”:“iOS”,“udid”:“c300cd776b5d7fca55350f724086e4f704dea0da”},“capabilities”:{“firstMatch”:[{“appium:automationName”:“XCUITest”,“appium:bundleId”:“com.apple.mobilesafari”,“deviceId”:“”,“appium:deviceName”:“Btp i7”,“appium:newCommandTimeout”:1800,“appium:noReset”:false,“platformName”:“ios”,“appium:platformVersion”:“15.5”,“realDeviceLogger”:“/Applications/Katalon Studio.app/Contents/Eclipse/configuration/resources/tools/deviceconsole”,“appium:udid”:“c300cd776b5d7fca55350f724086e4f704dea0da”,“appium:waitForAppScript”:“true;”,“appium:wdaLocalPort”:64223,“webKitDebugProxyPort”:“4723”}]}}e[39m
e[35m[BaseDriver]e[39m The following capabilities are not standard capabilities and should have an extension prefix:
e[35m[BaseDriver]e[39m deviceId
e[35m[BaseDriver]e[39m realDeviceLogger
e[35m[BaseDriver]e[39m webKitDebugProxyPort
e[35m[BaseDriver]e[39m chromedriverPort
e[35m[Appium]e[39m Appium v1.22.3 creating new XCUITestDriver (v3.59.0) session
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 realDeviceLogger
e[35m[BaseDriver]e[39m webKitDebugProxyPort
e[35m[BaseDriver]e[39m chromedriverPort
e[35m[BaseDriver]e[39m waitForAppScript
e[35m[BaseDriver]e[39m Session created with session id: 8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8
e[35m[XCUITest]e[39m Determining device to run tests on: udid: ‘c300cd776b5d7fca55350f724086e4f704dea0da’, real device: true
e[35m[WebDriverAgent]e[39m Using WDA path: ‘/Users/irashane/node_modules/appium/node_modules/appium-webdriveragent’
e[35m[WebDriverAgent]e[39m Using WDA agent: ‘/Users/irashane/node_modules/appium/node_modules/appium-webdriveragent/WebDriverAgent.xcodeproj’
e[35m[XCUITest]e[39m Setting up real device
e[35m[DevCon Factory]e[39m Requesting connection for device c300cd776b5d7fca55350f724086e4f704dea0da on local port 64223, device port 64223
e[35m[DevCon Factory]e[39m Successfully requested the connection for c300cd776b5d7fca55350f724086e4f704dea0da:64223
e[35e[35m[Appium]e[39m Received SIGTERM - shutting down
eceived SIGTERM - shutting down
on the device
e[35m[WebDriverAgent]e[39m WebDriverAgent does not need a cleanup. The sources are up to date (1652951495939 >= 1652951495939)
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m socket hang up
e[35m[WD Proxy]e[39m Determined the downstream protocol as ‘W3C’
e[35m[XCUITest]e[39m Skipping setting of the initial display orientation. Set the “orientation” capability to either “LANDSCAPE” or “PORTRAIT”, if this is an undesired behavior.
e[35m[Appium]e[39m New XCUITestDriver session created successfully, session 8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8 added to master session list
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[3e[35m[Appium]e[39m Received SIGTERM - shutting down
e[90me[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8e[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[XCUITest]e[39m Merging WDA caps over Appium caps for session detail response
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8 e[39me[32m200e[39m e[90m536 ms - 663e[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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8e[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[XCUITest]e[39m Merging WDA caps over Appium caps for session detail response
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8 e[39me[32m200e[39m e[90m1 ms - 663e[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[90m0 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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/timeoutse[39m
e[35m[HTTP]e[39m e[90m{“implicit”:60000}e[39m
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/timeouts e[39me[32m200e[39m e[90m1 ms - 14e[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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/screenshote[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/screenshot e[39me[32m200e[39m e[90m742 ms - 6914624e[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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/window/recte[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/window/rect e[39me[32m200e[39m e[90m205 ms - 48e[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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/screenshote[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/screenshot e[39me[32m200e[39m e[90m625 ms - 6914624e[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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/execute/synce[39m
e[35m[HTTP]e[39m e[90m{“script”:“mobile: viewportScreenshot”,“args”:}e[39m
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/execute/sync e[39me[32m200e[39m e[90m1516 ms - 5035004e[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/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/appium/device/activate_appe[39m
e[35m[HTTP]e[39m e[90m{“bundleId”:“com.apple.mobilesafari”}e[39m
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session/8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8/appium/device/activate_app e[39me[32m200e[39m e[90m949 ms - 14e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[Appium]e[39m Received SIGTERM - shutting down
e[35m[Appium]e[39m Closing session, cause was ‘The process has received SIGTERM signal’
e[35m[Appium]e[39m Removing session ‘8221f9f8-fc86-4f9b-a0b4-e1b4cd6964b8’ from our master session list
e[35m[DevCon Factory]e[39m Releasing connections for c300cd776b5d7fca55350f724086e4f704dea0da device on any port number
e[35m[DevCon Factory]e[39m Found cached connections to release: [“c300cd776b5d7fca55350f724086e4f704dea0da:64223”]
e[35m[DevCon Factory]e[39m Releasing the listener for ‘c300cd776b5d7fca55350f724086e4f704dea0da:64223’

2

Let me reproduce your issue with the version and get back to you soon

3

Hi,

Katalon has not fully supported Xcode 14. If you still want to set up, please refer to this document: Katalon Help Center. In case you cannot open Katalon, reach this doc Katalon Help Center. Thank you

4

Hi Elly. I’ve looked at your solutions referenced above and have followed all the steps. I have Appium 2.0 installed and have downloaded and installed your Katalon 8.5.4alpha. Because my machine is on MacOS Ventura, I’ve also followed the second set of steps to theoretically make 8.5.4alpha play nicely with it. However, when I run the terminal command mentioned in those instructions, I get the following response:

joshw@JoshW-MBP Contents % sh KatalonStudio_PE.sh
Starting at .
KatalonStudio_PE.sh: line 6: ./Eclipse/jre/Contents/Home/bin/java: Permission denied

I’ve checked my local permissions on that folder, and everything seems to indicate I can edit it. Is there something I’m missing that you’re aware of?

Thanks.

5

Can you try to put sudo before the argument? For example, sudo sh KatalonStudio_PE.sh

6

That idea makes a ton of sense, and I just tried it… but it didn’t work either. :confused: It resulted in the same permission error.

7

that idea is just silly.
may have sense in linux os context, but make no sense in MacOS context

8

Hi,

As far as I know, sudo can be used in MacOS as super user privilege. @joshw can you try other commands? In the meanwhile, I will try to find relevant tickets internally and if not be able to solve, I will raise the ticket. Back to you soon!

9

I have good news, Elly. :slight_smile: It seems, according to Katalon Help Center (and the fact that Katalon isn’t crashing on me), that Apple’s resolved the root problem. I’m able to launch that alpha version without second workaround.

1 Like