Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appium 1.7.1, WDA ServerURLHere->http://[...]:0<-ServerURLHere #9547

Closed
FrankThonig opened this issue Oct 27, 2017 · 5 comments
Closed

Appium 1.7.1, WDA ServerURLHere->http://[...]:0<-ServerURLHere #9547

FrankThonig opened this issue Oct 27, 2017 · 5 comments
Labels
ThirdParty upstream problems XCUITest regarding xcuitest driver

Comments

@FrankThonig
Copy link

The problem

WDA can generally be started via xcodebuild.

This works with the WDA:

From Log:
ServerURLHere->http://[...]:8100<-ServerURLHere

It does not work with the WDA:

  • coming with Appium 1.7.1

From Log:
ServerURLHere->http://[...]:0<-ServerURLHere

With Appium 1.7.1, the WDA does when being started by Appium when instantiating the Remote Webdriver in code without the desired_capabilities["webDriverAgentUrl"] being set.
However, going into the Appium log, copying the exact command line which is written there (used here in the "Details" section), and executing that command leads to the issue named above.

So, apparently, the call of the xcodebuild is not executed in exactly the same way for both:

  • by Appium during instantiation of Remote Webdriver
  • manually in shell

Environment

  • Appium version (or git revision) that exhibits the issue: 1.7.1 (also 1.6.6-beta)
  • Last Appium version that did not exhibit the issue (if applicable): 1.6.5
  • Desktop OS/version used to run Appium: macOS Sierra version 10.12.6
  • Node.js version (unless using Appium.app|exe): v8.3.0
  • Mobile platform/version under test: iOS 10.3
  • Real device or emulator/simulator: simulator
  • Appium CLI or Appium.app|exe: Appium CLI

Details

Command line, copied from Appium log and executed separately in shell:

xcodebuild build-for-testing test-without-building -project [...]/WebDriverAgent/WebDriverAgent.xcodeproj -scheme WebDriverAgentRunner -destination id=[...] IPHONEOS_DEPLOYMENT_TARGET=10.3 > "[...]/stdout.txt" 2> "[...]/stderr.txt"

Same issue occurrs when calling the build/test from Xcode GUI.

Link to Appium logs

Listing also WDA logs, because the issue is related to the specific WDA coming with Appium.

With issue for WDA in Appium 1.7.1, when using xcodebuild:

stdout_1_7_1.txt: https://gist.github.com/FrankThonig/141b7ba87b9b85e67974172129706779
stderr_1_7_1.txt: https://gist.github.com/FrankThonig/113b45c17858ee431d9cc527ad7d8acf
xcode_1_7_1.txt: https://gist.github.com/FrankThonig/6e2dfbd3efdb59710340d27ba38c8e0f

Without issue for WDA in Appium 1.7.1, when being started by Appium without desired_capabilities["webDriverAgentUrl"] being set:

appium_1_7_1.txt: https://gist.github.com/FrankThonig/0d90f9ab993084a51de3e4d8ccb8c65b

Without issue for WDA in Appium 1.6.5, when using xcodebuild:

stdout_1_6_5.txt: https://gist.github.com/FrankThonig/65901607854f709ed3c35fab1906857c
stderr_1_6_5.txt: https://gist.github.com/FrankThonig/ea7913aa5c3ec3bebe1173f2cdf1cfd0
xcode_1_6_5.txt: https://gist.github.com/FrankThonig/62c622841f7f189254bc928f64c71628

@mykola-mokhnach
Copy link
Collaborator

add USE_PORT=8100 at the beginning of xcodebuild execution command

@mykola-mokhnach mykola-mokhnach added ThirdParty upstream problems XCUITest regarding xcuitest driver labels Oct 27, 2017
@FrankThonig
Copy link
Author

FrankThonig commented Oct 27, 2017

@mykola-mokhnach
thank you very much.

this is exactly what i was looking for. i did not find any documentation on how to do this.

WDA now runs as expected on the respective port.

@mykola-mokhnach
Copy link
Collaborator

@FrankThonig
Copy link
Author

thank you very much for that information

@lock
Copy link

lock bot commented Apr 25, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ThirdParty upstream problems XCUITest regarding xcuitest driver
Projects
None yet
Development

No branches or pull requests

2 participants