/usr/local/lib/node_modules/appium/node_modules/appium-webdriveragent/WebDriverAgent.xcodeproj
/usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/node_modules/appium-webdriveragent/WebDriverAgent.xcodeproj
In my opinion, these discrepancies should be emphasized in docs or removed to prevent such situation
The second place is the right one.
Only appium-xcuitest-driver/node_modules/appium-webdriveragent/ should be the right root folder for WDA for Appium 1.16
The other one is probably used by other drivers (most likely Flutter, which depends on the older module version)
Only node_modules/appium-webdriveragent/ should be the right root folder for WDA for Appium 1.16
The other one is probably used by other drivers (most likely Flutter)
If the second place is not signed it fails for me
@mykola-mokhnach enabling Xcodebuild logging from capabilities needs to make changes to the Core of our framework which is not belongs to me (it will take some time)
Do you have any other suggestions?
In the log it is clearly visible which WDA path is used:
2020-01-13 11:54:33:666 [XCUITest] Using WDA path: '/usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/node_modules/appium-webdriveragent'
Why then??
it actually depends on npm which folder is put to the modules root and which one is put under appium-xcuitest-driver
Although you are right, the documentation should be updated to reflect this case
Appium GUI 1.15.1 and 1.16.0 - Installs WebDriverAgentRunner on real iOS device - Installs ipa on real device - then removes them an throws bundleId error
#13894
Hello,
The WebdriverAgent isn't running on a simulator for me. I'm working through the Appium Pro Workshop and on the Appium Sessions section. Everything works as expected with an Android Simulator. With IOS, the WDA and application get installed, but the Appium Server can't connect to the WebdriverAgent.
[debug] [XCUITest] Starting WebDriverAgent initialization with the synchronization key 'XCUITestDriver'
[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://localhost:8100/status] with no body
[WD Proxy] Got an unexpected response with status undefined: {"errno":-61,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":8100}
Appium tries repeatedly but fails to connect. I verified nothing is running on port 8100 before during or after I run the IOSCapabilitiesTest.
I know this bug is marked as closed but I don't see a workaround or fix submitted above.
Any help would be much appreciated. Thank you.
Is there anyway to change where http://localhost:8100/status or 127.0.0.1","port":8100 are going? My appium server says 0.0.0.0:4723 so I think a problem might be reaching out to the wrong port/ip.
Eventually it errors out with:
[info] �[35m[WD Proxy]�[39m Got response with unknown status: {"code":"ECONNRESET"}[error] �[35m[Xcode]�[39m 2020-08-11 09:45:21.348 xcodebuild[22597:58545] DTDeviceKit: Could not start house arrest service for app identifier com.facebook.WebDriverAgentRunner.xctrunner [Error Domain=com.apple.dtdevicekit Code=-402653093 "Xcode encountered an error" UserInfo={NSLocalizedFailureReason=Too many instances of this service are already running.
I also faced this issue . In my situation, I have installed appium both via npm as well as Appium Desktop.
I was running Appium server via Appium Desktop and was constantly getting this error.
I checked logs and found that WebDriverAgent.xcodeproj was located at /Applications/Appium Server GUI.app/Contents/Resources/app/node_modules/appium/node_modules/appium-webdriveragent/ in case of Appium Desktop and at /Users/username/.nvm/versions/node/v_nodeversion_/lib/node_modules/appium/node_modules/appium-webdriveragent (I installed node via nvm) for appium installed via node.
I followed steps given in https://appium.io/docs/en/drivers/ios-xcuitest-real-devices/#full-manual-configuration for both locations and automation worked for me. ( Note: App signing was done using Apple developer account).
