Open Hcu opened 3 years ago
WDA is the main reason go-ios has xctest support :-D What iOS version are you running this on?
PS: instead of iproxy you should be good using go-ios forward, one less binary to maintain :-D
Ah yes, thanks for the tip :), I'm running iOS 13.1
And you are using an unmodified WDA build? That is super weird, it should actually work
The only difference made to the WDA build is the provisioning profiles used to sign it.
As I don't have a device where I can seem to get WDA fully started, just wondering what the trace output should look like for a successful WDA launch to perhaps spot where the difference occurs ?
Also this line: INFO[0001] 2021-11-22 21:00:21.302611-0500 WebDriverAgentRunner-Runner[3115:2987381] Unable to load configuration data from specified path /; error: The file “System@snap-1004721” couldn’t be opened because you don’t have permission to view it.
Is this expected output or could this be somehow related ?
Can you run dproxy, and get me a dump of the xcode test execution that works, and one with the broken device? That way I can look into what is going on.
I just merged a few WDA fixes. Please try again with the latest release.
Thanks Daniel, currently no longer have access to the devices, but as soon as I do, I will give the latest version a go!
I'm trying to execute the runwda command on a mac machine but it does not seem to fully start up the WDA process.
Why am I running this on a mac ? Well ultimately, I would like to have a linux box that has an SSH tunnel to the mac and simply use unix socket forwarding to forward
/var/run/usbmuxd
to expose the devices to the linux machine. At first I was performingios runwda
from the linux box with the ssh tunnelled/var/run/usbmuxd
, but that didn't work, so I figured, let's try it on the mac itself, and also there, it seems to 'hang'. It seems to work 'partially' as in, the process starts, but I never get output that the wda server is up and running with the device ip and the wda port printed out in the output.Here is the output of the runwda command on the mac with tracing enabled.
This is where the process seems to get 'stuck'.
In a second terminal, I run
iproxy 8100 8100 --udid 40xxxxxxxxxxx
and afterwards perform a curl to http://localhost:8100, but get the following output:If I run appium and create a session with the same WebDriverAgent.xcproj that was used to generate the app that I trigger through runwda , appium starts fine and the webdriveragent starts up without issues and prints out
WebDriverAgent is ready to accept commands
with the ip of the device. So I believe the WebDriverAgent.ipa is not the culprit.Not sure if running the Webdriveragent is supposed to be a supported use case for go-ios, but if anyone has any ideas, I'm all ears! Cheers!