-
Notifications
You must be signed in to change notification settings - Fork 420
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
【 iOS 】获取 Hybrid 页面元素时,发现找不到元素。通过打印日志发现,获取到的 driver 只有 Native,没有 WebDriver #872
Comments
This is the translated issue: [ios] When I get a Hybrid page element, I found that I could not find the element. By printing the log, the driver obtained is only native, no WebDriver
[ios] When I get a Hybrid page element, I found that I could not find the element. By printing the log, the driver obtained is only native, there is no WebDriver, and the prompt "'Cannot find any Webview'" |
我也遇到同样的问题,现在无法操作ios webview,已经找了很久的问题了,还没有解决,求回复 |
This is the translated issue comment: @zyq198764 I also encountered the same problem, can not operate ios webview now, has been looking for a long time, and has not resolved, ask for a reply |
macaca doctor? |
+1 在 webview 页面获取 contexts 时日志如下:
单独试了下 ios_webkit_debug_proxy,获取到的 http://localhost:9221/json 为空(https://github.com/google/ios-webkit-debug-proxy#can-not-see-simulator 已确保这几项都按文档操作了) 看到 IWDP 也有类似的 issue google/ios-webkit-debug-proxy#250 |
This is the translated issue comment: @louiseyang +1 The logs when getting contexts on the webview page are as follows:
I tried ios_webkit_debug_proxy separately and got http://localhost:9221/json empty (https://github.com/google/ios-webkit-debug-proxy#can-not-see-simulator Items are manipulated by document) I see a similar issue with IWDP google/ios-webkit-debug-proxy#250 |
This is the translated issue comment: @xudafeng Such as a recent update |
在 iOS 设备 Safari 浏览器中,获取 WebView 页面元素时,发现定位不到元素。通过打印日志发现,获取到的 driver 只有 NATIVE_APP,没有 WebDriver,提示 『'Cannot find any Webview'』
Case Demo:
Case结果:
Logs 输出 :contexts: ["NATIVE_APP"],没有 webview
@xudafeng 求支持
The text was updated successfully, but these errors were encountered: