You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
When connecting to the mcloud hub the Appium Inspector tries to connnect to WDA mjpeg port using hubs ip address (this behavior can be seen using Wireshark). As a result the Appium inspector loads only the list of elements and shows the screen preview loading as shown in the screen below:
This issue is only when you try to connect to iOS devices.
Setup:
MCloud 2.5.3
MCloud-Agent 2.5.5 (tested on Mac and ubuntu)
Appium Inspector 2023.8.4
IPhone 14 with iOS 16.0
Edit:
In an attempt to find a solution for this problem, I changed the zebrunner-farm script to use 2 additional unique parameters for wda_port and mjpeg_port for ios containers with port fowarding. Thanks to this, I am able to establish a direct connection with the device using the ip:port from "remoteHost" but still no luck with finding why the hub forwards everything for android but not for ios.
The text was updated successfully, but these errors were encountered:
Hi,
When connecting to the mcloud hub the Appium Inspector tries to connnect to WDA mjpeg port using hubs ip address (this behavior can be seen using Wireshark). As a result the Appium inspector loads only the list of elements and shows the screen preview loading as shown in the screen below:
This issue is only when you try to connect to iOS devices.
Setup:
MCloud 2.5.3
MCloud-Agent 2.5.5 (tested on Mac and ubuntu)
Appium Inspector 2023.8.4
IPhone 14 with iOS 16.0
Edit:
In an attempt to find a solution for this problem, I changed the zebrunner-farm script to use 2 additional unique parameters for wda_port and mjpeg_port for ios containers with port fowarding. Thanks to this, I am able to establish a direct connection with the device using the ip:port from "remoteHost" but still no luck with finding why the hub forwards everything for android but not for ios.
The text was updated successfully, but these errors were encountered: