Android
The WebView HTML UI capture may fail with the following error message:
Failed to get sockets matching: @webview_devtools_remote_.*30604 (make sure the app has its WebView configured for debugging)
In this case, it is possible that setWebContentsDebuggingEnabled(true) is being called within the app. Refer here, and check whether setWebContentsDebuggingEnabled(true) is being called.
iOS
There may be cases where the following kinds of error messages appear multiple times in the “Appium Console”.
[WD Proxy] Got response with status 404: {
[WD Proxy] "value" : {
[WD Proxy] "error" : "no such alert",
[WD Proxy] "message" : "An attempt was made to operate on a modal dialog when one was not open",
[WD Proxy] "traceback" : ""
[WD Proxy] },
[WD Proxy] "sessionId" : "0B4FC99E-DE0F-4E68-B7FC-C99034BA43FF"
[WD Proxy] }
[W3C] Matched W3C error code 'no such alert' to NoSuchAlertError
This is because Safari, which is used internally, is temporarily hung. As far as our investigation reveals, this seems to happen when using a real device/simulator of below iOS 14.2 and the size of HTML loaded by WebView exceeds about 3000 lines. So far, we have not found a workaround other than reviewing the HTML size. As far as we have confirmed here, the actual "scanning WebView elements as HTML" process seems to be complete after waiting about 5–6 minutes. However, the same problem may occur when running tests.