The webview socket not correct when I use appium switch to the webview(WeChat applet @xweb_devtools_remote_22599).

[jac...@gmail.com]

Hello,

My webview process is com.tencent.mm:appbrand0, the socket is @xweb_devtools_remote_22599 not @webview_devtools_remote_22599
because the view layer is rendered by the WeChat self-developed XWeb engine based on the Mobile Chrome 67 kernel.

But the Chromedriver try to get sockets matching: @webview_devtools_remote_.*22599, it failed.

I think this is an enhancement for Chromedriver, the socket name should be obtained from the system, not @webview_devtools_remote_.*+PID

For further details, you can see the log in my issue here: https://github.com/appium/appium/issues/13443.

Looking forward to your reply！

[jac...@gmail.com]

I think this is an enhancement for Chromedriver, the socket name should be obtained from the system, not @webview_devtools_remote_.*+PID.

"adb shell cat /proc/net/unix | grep PID" is better. 

[T Crichton]

Yes, this would be an enhancement, but ChromeDriver is maintained by a small team, and unfortunately we can only add features demanded by large number of users. I am sorry for any inconveniences this might cause.

We believe the solution proposed would not be reliable. It is possible for an app to have multiple sockets, for example.

[jac...@gmail.com]

Maybe an app to have multiple sockets, but an socket PID for an socket, your solution now is ("@webview_devtools_remote_.*%d", pid).

We have already got the socket PID, the socket name should be changed to  "name=adb shell cat /proc/net/unix | grep PID" .

The prefix not always be "@webview_devtools_remote_", I think the socket real name is better.