When i am trying to run my mobile app automation test on iOS device, I am getting error in appium log:
2022-04-12 12:40:14:687 - e[35m[WebDriverAgent]e[39m xcodebuild exited with code ‘65’ and signal ‘null’
2022-04-12 12:40:14:688 - [debug] e[35m[BaseDriver]e[39m Event ‘wdaStartFailed’ logged at 1649767214688 (15:40:14 GMT+0300 (Eastern European Summer Time))
2022-04-12 12:40:14:688 - [debug] e[35m[XCUITest]e[39m Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65
2022-04-12 12:40:14:688 - [debug] e[35m[XCUITest]e[39m xcodebuild error message:
2022-04-12 12:40:14:688 - [debug] e[35m[XCUITest]e[39m . Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
2022-04-12 12:40:14:688 - e[35m[XCUITest]e[39m Quitting and uninstalling WebDriverAgent
2022-04-12 12:40:14:688 - e[35m[WebDriverAgent]e[39m Shutting down sub-processes
2022-04-12 12:40:14:853 - [debug] e[35m[WebDriverAgent]e[39m No WDAs on the device.
2022-04-12 12:40:14:854 - e[35m[XCUITest]e[39m {}
2022-04-12 12:40:14:854 - e[35m[DevCon Factory]e[39m Releasing connections for 00008030-001E65E90ADB802E device on any port number
2022-04-12 12:40:14:854 - e[35m[DevCon Factory]e[39m Found cached connections to release: [“00008030-001E65E90ADB802E:5335”]
2022-04-12 12:40:14:854 - e[35m[DevCon Factory]e[39m Releasing the listener for ‘00008030-001E65E90ADB802E:5335’
2022-04-12 12:40:14:854 - [debug] e[35m[iProxy@00008030:5335]e[39m Closing the connection
2022-04-12 12:40:14:855 - [debug] e[35m[DevCon Factory]e[39m Cached connections count: 0
2022-04-12 12:40:14:855 - [debug] e[35m[XCUITest]e[39m Not clearing log files. Use clearSystemFiles capability to turn on.
2022-04-12 12:40:14:855 - e[35m[iProxy@00008030:5335]e[39m The connection has been closed
2022-04-12 12:40:14:856 - [debug] e[35m[BaseDriver]e[39m Event ‘newSessionStarted’ logged at 1649767214856 (15:40:14 GMT+0300 (Eastern European Summer Time))
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m Encountered internal error running command: Error: Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m xcodebuild error message:
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m . Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m at quitAndUninstall (/opt/homebrew/lib/node_modules/appium/node_modules/appium-xcuitest-driver/lib/driver.js:585:15)
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m at /opt/homebrew/lib/node_modules/appium/node_modules/appium-xcuitest-driver/lib/driver.js:620:11
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m at wrapped (/opt/homebrew/lib/node_modules/appium/node_modules/asyncbox/lib/asyncbox.js:60:13)
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m at retry (/opt/homebrew/lib/node_modules/appium/node_modules/asyncbox/lib/asyncbox.js:43:13)
2022-04-12 12:40:14:856 - [debug] e[35m[W3C]e[39m at retryInterval (/opt/homebrew/lib/node_modules/appium/node_modules/asyncbox/lib/asyncbox.js:70:10)
2022-04-12 12:40:14:858 - [debug] e[35m[W3C]e[39m at /opt/homebrew/lib/node_modules/appium/node_modules/appium-xcuitest-driver/lib/driver.js:600:7
Can any one please let me know what it means and the solution to overcome.
When I run xcode build successfully.
system used: Mac M1
Xcode version : 13.3
appium version: 1.22.3
iOS version: 15.4
I have second Early Mac 2015 with the same configuration and everything works.
Only difference is that on M1 appium path: ‘/opt/homebrew/bin/appium’ and on second older Mac appium path: ‘user/local/bin/appium’
I set additional capabilities:
addMobileDesiredCapabilities.setCapability(“xcodeOrgId”, “SWQA3DF4FQ”);
addMobileDesiredCapabilities.setCapability(“xcodeSigningId”, “iPhone Developer”);
And created a file ‘.xconfig’ and set content:
DEVELOPMENT_TEAM = SWQA3DF4FQ
CODE_SIGN_IDENTITY = iPhone Developer
Run the test and got the same error message in appium log, and WebDriverAgent didn’t install on iOS device, my app was installed without WebDriverAgent on device
I’m using iOS.yaml file where are set all device config:
serverPort: 8006
appiumProxyPort: 15000
appium:
Hi Facing this issue for ios 16, xcode 14 build. tried above suggestions still facing the same and this is happening while trying to inspect on simulator
{
“platformName”: “iOS”,
“appium:platformVersion”: “16.0”,
“appium:automationName”: “XCUITest”,
“appium:bundleId”: “com.sap.epm.**”,
“appium:deviceName”: “iPhone 14 Pro Max”
}
Device cap
Thanks a lot for the suggestions, i tried but i am still facing the issue, i get error 65 even after following the latest version of webdriver agent, do i need it to be replacing the old webdriver agent within the appium content?
You will face this issue on MAC because WDA present inside Appium is not compatible with your XCode 14.2. When you install Appium, it is equipped with latest WDA at the time of released version for example appium 1.22.3 will come with WebdriverAgent 3.17.0 You can check WDA repo for compatible XCode [WDA link]. After 12.4 they have stopped mentioning XCode compatibility. Here are the steps to be followed to replace older WDA to latest WDA
I ran into the same problem with iOS 16.4. Here is how I solved it:
In case of any OS upgrade(iOS), the framework gets disturbed as the other apps(Appium version/xcode/mac os) become unsupported.
We might get errors like ‘Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65’ or ‘A valid provisioning profile for this executable was not found.’
Check the signing and capabilities for webdriveragentrunner and webdriveragentlib, it should be signed in using a proper developer account
Try running the tests again and check if the error isn’t coming anymore. In case the same errors still comes we need to do the next steps mentioned below