-
-
Notifications
You must be signed in to change notification settings - Fork 424
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
return current status to ensure appium uses cached WDA #909
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch @KazuCocoa
Thanks
* return current status to ensure appium uses cached WDA * update docstring * add await
if I set WDA_LOCAL_PORT which not default port: 8100, it seems the useNewWDA not working? could you please help to check? |
Do you mean appium-xcuitest-driver/lib/driver.js Lines 751 to 754 in 92a7513
|
Here is the scene: |
Fix appium/appium#12259
Based on current behaviour in re-use WDA is below. Try to call
[XCUITest] Using provided WebdriverAgent at 'http://localhost:8100/'
even if Appium already ensured the response likeGot response with status 200
.return await this.xcodebuild.start();
called inasync launch (sessionId) {
returns current/status
, but thelaunch
function does not retun such status ifthis.webDriverAgentUrl
is set.It means
this.cachedWdaStatus
inappium-xcuitest-driver/lib/driver.js
Line 485 in 30d8cef
await this.wda.setupCaching(this.opts.updatedWDABundleId);
inappium-xcuitest-driver/lib/driver.js
Line 459 in 30d8cef
After this PR, the
this.cachedWdaStatus
can get current running WDA status like below. As the result, xcuitest-driver can use existing WDA instance in the new session.