Issue creating a session with XCUITest 4.3.7
See original GitHub issueThe problem
Hi all,
I have tried updating the iOS driver with the command
appium driver update xcuitest
and after updating from the version 4.3.5 to the 4.3.7. It seems that at least this driver is correct. Nevertheless, I’m trying just to open an App on an iOS simulator with the Appium Inspector and I’m facing several issues.
The simulator isn’t opened as with Appium server GUI. Appium log shows this error message Encountered internal error running command: Error: The simulator ---- has failed to finish booting after 120s. The appium Inspector reports a timeout error. After a while, it seems that Appium tries again to install the WDA on the simulator and it starts the common connecting retries like:
Proxying [GET /status] to [GET http://127.0.0.1:8100/status] with no body connect ECONNREFUSED 127.0.0.1:8100
But instead to opening the simulator or connecting as it’s the normal workflow with Appium 1.X. Maybe it’s all related to the issue that the simulator is not opened, but I’m not sure. I have also tried opening manually the simulator but the behavior is the same.
Environment
- Appium version (or git revision) that exhibits the issue: v2.0.0-beta.30
- Last Appium version that did not exhibit the issue (if applicable): I’ve tried Appium Server GUI v1.22 without any issue.
- Desktop OS/version used to run Appium: MacOS
- Mobile platform/version under test: iOS
- Real device or emulator/simulator: Simulator (iPhone 11 Pro Max with iOS 14.2)
Code To Reproduce Issue [ Good To Have ]
I’ve used the following capabilities for the test.
{ "platformName": "iOS", "deviceName": "iPhone 11 Pro Max", "automationName": "XCUITest", "language": "es", "locale": "ES", "platformVersion": "14.2" }
Thank you for your support.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (2 by maintainers)
Thank you @KazuCocoa for your comments, I have tried to run the xcodebuild manually and I’ve found the issue. My current user doesn’t have an administrative role, so to install appium 2.0 I had to change to a sudoer user.
At this point everything is clear, but if I install the drivers and plugins with this admin user, they’ll be installed in the .appium folder inside the current user folder:
/Users/AdminUser/.appium/node_modules/.......
and if I try to run appium with my normal user, these folders don’t exist.
/Users/TestUser/.appium/node_modules/.......
I’m not sure if it’s an issue or if the documentation must advice about this possible situation.
Anyway… after installing all plugins & drivers with my common user… everything is working as expected. Thank you for your support
The default place as the user’s home is expected behavior. You can customize it with APPIUM_HOME environment variable. (We’re still working on documentation stuff, but doc will have such description about
.appium
home)