How can i switch native app to mini program webview?

johny · October 18, 2019, 4:46am

i’ve searched servral topics about this, but make any sense,when i switch to webview, the appium log shows there is no webview i can change,here is my code and capabilities:

[Appium] Appium v1.13.0 creating new AndroidUiautomator2Driver (v1.33.1) session
[Appium] Capabilities:
[Appium] platformName: Android
[Appium] deviceName: 36c02a5
[Appium] platformVersion: 9
[Appium] automationName: UiAutomator2
[Appium] appPackage: com.tencent.mm
[Appium] appActivity: .ui.LauncherUI
[Appium] ChromeOptions: {
[Appium] androidProcess: com.tencent.mm:appbrand0
[Appium] }
[Appium] noReset: true
[Appium] fullReset: false

code:

“”“点击小程序按钮”“”
minipro = “小程序”
el_minipro = self.driver.find_element_by_android_uiautomator(“new UiSelector().text("”+minipro+“")”)
print(“页面上定位到小程序元素吗？:%s” % el_minipro.is_displayed())
if el_minipro.is_displayed():
el_minipro.click()
“”“切换页面活动值小程序列表显示页面”“”
self.driver.wait_activity(“.plugin.appbrand.ui.AppBrandLauncherUI”, THINK_TIME)
sleep(THINK_TIME)
print(“页面的所有模式”, self.driver.contexts)
target_minipro = “咖啡外卖”
el_target = action().find_byUiautormator(“textContains”, target_minipro)
print(“页面上定位到target小程序元素吗？:%s” % el_target.is_displayed())
if el_target.is_displayed():
el_target.click()
“”“点击小程序进入页面，切换进入webview页面”“”
self.driver.switch_to.context(“WEBVIEW_com.tencent.mm:appbrand0”)
sleep(10)
print(“当前页面的模式为：%s” % self.driver.context)
menu = “新品咖啡”
el_menu = action().find_byUiautormator(“text”, menu)
print(“页面上定位到小程序menu元素吗？:%s” % el_menu.is_displayed())
if el_menu.is_displayed():
el_menu.click()

appium log:

[HTTP] → POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element
[HTTP] {“using”:“-android uiautomator”,“value”:“new UiSelector().text("小程序")”}
[W3C (22d1ec00)] Calling AppiumDriver.findElement() with args: [“-android uiautomator”,“new UiSelector().text("小程序")”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -android uiautomator
[BaseDriver] Waiting up to 0 ms for condition
[WD Proxy] Matched ‘/element’ to command name ‘findElement’
[WD Proxy] Proxying [POST /element] to [POST http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element] with body: {“strategy”:“-android uiautomator”,“selector”:“new UiSelector().text("小程序")”,“context”:“”,“multiple”:false}
[WD Proxy] Got response with status 200: {“sessionId”:“394e282f-5662-4e81-83ba-c09ef94f8d0c”,“status”:0,“value”:{“ELEMENT”:“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”}}
[W3C (22d1ec00)] Responding to client with driver.findElement() result: {“element-6066-11e4-a52e-4f735466cecf”:“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”,“ELEMENT”:“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”}
[HTTP] ← POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element 200 120 ms - 137
[HTTP]
[HTTP] → GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/displayed
[HTTP] {}
[W3C (22d1ec00)] Calling AppiumDriver.elementDisplayed() with args: [“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[WD Proxy] Matched ‘/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/attribute/displayed’ to command name ‘getAttribute’
[WD Proxy] Proxying [GET /element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/attribute/displayed] to [GET http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/attribute/displayed] with body: {}
[WD Proxy] Got response with status 200: “{"sessionId":"394e282f-5662-4e81-83ba-c09ef94f8d0c","status":0,"value":"true"}”
[W3C (22d1ec00)] Responding to client with driver.elementDisplayed() result: true
[HTTP] ← GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/displayed 200 77 ms - 14
[HTTP]
[HTTP] → GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/displayed
[HTTP] {}
[W3C (22d1ec00)] Calling AppiumDriver.elementDisplayed() with args: [“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[WD Proxy] Matched ‘/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/attribute/displayed’ to command name ‘getAttribute’
[WD Proxy] Proxying [GET /element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/attribute/displayed] to [GET http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/attribute/displayed] with body: {}
[WD Proxy] Got response with status 200: “{"sessionId":"394e282f-5662-4e81-83ba-c09ef94f8d0c","status":0,"value":"true"}”
[W3C (22d1ec00)] Responding to client with driver.elementDisplayed() result: true
[HTTP] ← GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/displayed 200 116 ms - 14
[HTTP]
[HTTP] → POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/click
[HTTP] {“id”:“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”}
[W3C (22d1ec00)] Calling AppiumDriver.click() with args: [“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[WD Proxy] Matched ‘/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/click’ to command name ‘click’
[WD Proxy] Proxying [POST /element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/click] to [POST http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/click] with body: {“element”:“a41c39cb-d50b-4899-9e47-aba5cd6c33e9”}
[WD Proxy] Got response with status 200: {“sessionId”:“394e282f-5662-4e81-83ba-c09ef94f8d0c”,“status”:0,“value”:true}
[W3C (22d1ec00)] Responding to client with driver.click() result: true
[HTTP] ← POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/a41c39cb-d50b-4899-9e47-aba5cd6c33e9/click 200 2509 ms - 14
[HTTP]
[HTTP] → GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/appium/device/current_activity
[HTTP] {}
[W3C (22d1ec00)] Calling AppiumDriver.getCurrentActivity() with args: [“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[ADB] Getting focused package and activity
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell dumpsys window windows’
[W3C (22d1ec00)] Responding to client with driver.getCurrentActivity() result: “.plugin.appbrand.ui.AppBrandLauncherUI”
[HTTP] ← GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/appium/device/current_activity 200 265 ms - 50
[HTTP]
[HTTP] → GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/contexts
[HTTP] {}
[W3C (22d1ec00)] Calling AppiumDriver.getContexts() with args: [“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[AndroidDriver] Getting a list of available webviews
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell cat /proc/net/unix’
[AndroidDriver] Found webviews:
[AndroidDriver] Available contexts: [“NATIVE_APP”]
[W3C (22d1ec00)] Responding to client with driver.getContexts() result: [“NATIVE_APP”]
[HTTP] ← GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/contexts 200 120 ms - 24
[HTTP]
[HTTP] → POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element
[HTTP] {“using”:“-android uiautomator”,“value”:“new UiSelector(). textContains("咖啡外卖")”}
[W3C (22d1ec00)] Calling AppiumDriver.findElement() with args: [“-android uiautomator”,“new UiSelector(). textContains("咖啡外卖")”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -android uiautomator
[BaseDriver] Waiting up to 0 ms for condition
[WD Proxy] Matched ‘/element’ to command name ‘findElement’
[WD Proxy] Proxying [POST /element] to [POST http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element] with body: {“strategy”:“-android uiautomator”,“selector”:“new UiSelector(). textContains("咖啡外卖")”,“context”:“”,“multiple”:false}
[WD Proxy] Got response with status 200: {“sessionId”:“394e282f-5662-4e81-83ba-c09ef94f8d0c”,“status”:0,“value”:{“ELEMENT”:“e627d987-4273-4fca-92f9-dc49cedae90e”}}
[W3C (22d1ec00)] Responding to client with driver.findElement() result: {“element-6066-11e4-a52e-4f735466cecf”:“e627d987-4273-4fca-92f9-dc49cedae90e”,“ELEMENT”:“e627d987-4273-4fca-92f9-dc49cedae90e”}
[HTTP] ← POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element 200 87 ms - 137
[HTTP]
[HTTP] → GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/e627d987-4273-4fca-92f9-dc49cedae90e/displayed
[HTTP] {}
[W3C (22d1ec00)] Calling AppiumDriver.elementDisplayed() with args: [“e627d987-4273-4fca-92f9-dc49cedae90e”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[WD Proxy] Matched ‘/element/e627d987-4273-4fca-92f9-dc49cedae90e/attribute/displayed’ to command name ‘getAttribute’
[WD Proxy] Proxying [GET /element/e627d987-4273-4fca-92f9-dc49cedae90e/attribute/displayed] to [GET http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element/e627d987-4273-4fca-92f9-dc49cedae90e/attribute/displayed] with body: {}
[WD Proxy] Got response with status 200: “{"sessionId":"394e282f-5662-4e81-83ba-c09ef94f8d0c","status":0,"value":"true"}”
[W3C (22d1ec00)] Responding to client with driver.elementDisplayed() result: true
[HTTP] ← GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/e627d987-4273-4fca-92f9-dc49cedae90e/displayed 200 72 ms - 14
[HTTP]
[HTTP] → GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/e627d987-4273-4fca-92f9-dc49cedae90e/displayed
[HTTP] {}
[W3C (22d1ec00)] Calling AppiumDriver.elementDisplayed() with args: [“e627d987-4273-4fca-92f9-dc49cedae90e”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[WD Proxy] Matched ‘/element/e627d987-4273-4fca-92f9-dc49cedae90e/attribute/displayed’ to command name ‘getAttribute’
[WD Proxy] Proxying [GET /element/e627d987-4273-4fca-92f9-dc49cedae90e/attribute/displayed] to [GET http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element/e627d987-4273-4fca-92f9-dc49cedae90e/attribute/displayed] with body: {}
[WD Proxy] Got response with status 200: “{"sessionId":"394e282f-5662-4e81-83ba-c09ef94f8d0c","status":0,"value":"true"}”
[W3C (22d1ec00)] Responding to client with driver.elementDisplayed() result: true
[HTTP] ← GET /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/e627d987-4273-4fca-92f9-dc49cedae90e/displayed 200 54 ms - 14
[HTTP]
[HTTP] → POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/e627d987-4273-4fca-92f9-dc49cedae90e/click
[HTTP] {“id”:“e627d987-4273-4fca-92f9-dc49cedae90e”}
[W3C (22d1ec00)] Calling AppiumDriver.click() with args: [“e627d987-4273-4fca-92f9-dc49cedae90e”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[WD Proxy] Matched ‘/element/e627d987-4273-4fca-92f9-dc49cedae90e/click’ to command name ‘click’
[WD Proxy] Proxying [POST /element/e627d987-4273-4fca-92f9-dc49cedae90e/click] to [POST http://localhost:8200/wd/hub/session/394e282f-5662-4e81-83ba-c09ef94f8d0c/element/e627d987-4273-4fca-92f9-dc49cedae90e/click] with body: {“element”:“e627d987-4273-4fca-92f9-dc49cedae90e”}
[WD Proxy] Got response with status 200: {“sessionId”:“394e282f-5662-4e81-83ba-c09ef94f8d0c”,“status”:0,“value”:true}
[W3C (22d1ec00)] Responding to client with driver.click() result: true
[HTTP] ← POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/element/e627d987-4273-4fca-92f9-dc49cedae90e/click 200 2548 ms - 14
[HTTP]
[HTTP] → POST /wd/hub/session/22d1ec00-f881-4d21-aaf2-15893928ff14/context
[HTTP] {“name”:“WEBVIEW_com.tencent.mm:appbrand0”}
[W3C (22d1ec00)] Calling AppiumDriver.setContext() with args: [“WEBVIEW_com.tencent.mm:appbrand0”,“22d1ec00-f881-4d21-aaf2-15893928ff14”]
[AndroidDriver] Getting a list of available webviews
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell cat /proc/net/unix’
[AndroidDriver] Found webviews:
[AndroidDriver] Available contexts: [“NATIVE_APP”]
[W3C (22d1ec00)] Encountered internal error running command: NoSuchContextError: No such context found.

johny · October 18, 2019, 7:04am

i’ve known why webviews are blank. cause i forgot to open debug mode.
now , the webview can response normally, but i met another problem again:

[HTTP] → GET /wd/hub/session/98b7c50c-0974-4006-96a9-24bec4cb229b/contexts
[HTTP] {}
[W3C (98b7c50c)] Calling AppiumDriver.getContexts() with args: [“98b7c50c-0974-4006-96a9-24bec4cb229b”]
[AndroidDriver] Getting a list of available webviews
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell cat /proc/net/unix’
[AndroidDriver] WEBVIEW_14029 mapped to pid 14029
[AndroidDriver] Getting process name for webview
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell ps’
[AndroidDriver] Parsed pid: ‘14029’ pkg: ‘com.tencent.mm:tools’ from
[AndroidDriver] USER PID PPID VSZ RSS WCHAN ADDR S NAME
[AndroidDriver] u0_a172 14029 632 2511952 330684 0 0 S com.tencent.mm:tools
[AndroidDriver] Returning process name: ‘com.tencent.mm:tools’
[AndroidDriver] Found webviews: [“WEBVIEW_com.tencent.mm:tools”]
[AndroidDriver] Available contexts: [“NATIVE_APP”,“WEBVIEW_com.tencent.mm:tools”]
[W3C (98b7c50c)] Responding to client with driver.getContexts() result: [“NATIVE_APP”,“WEBVIEW_com.tencent.mm:tools”]
[HTTP] ← GET /wd/hub/session/98b7c50c-0974-4006-96a9-24bec4cb229b/contexts 200 281 ms - 55
[HTTP]
[HTTP] → POST /wd/hub/session/98b7c50c-0974-4006-96a9-24bec4cb229b/context
[HTTP] {“name”:“WEBVIEW_com.tencent.mm:tools”}
[W3C (98b7c50c)] Calling AppiumDriver.setContext() with args: [“WEBVIEW_com.tencent.mm:tools”,“98b7c50c-0974-4006-96a9-24bec4cb229b”]
[AndroidDriver] Getting a list of available webviews
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell cat /proc/net/unix’
[AndroidDriver] WEBVIEW_14029 mapped to pid 14029
[AndroidDriver] Getting process name for webview
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell ps’
[AndroidDriver] Parsed pid: ‘14029’ pkg: ‘com.tencent.mm:tools’ from
[AndroidDriver] USER PID PPID VSZ RSS WCHAN ADDR S NAME
[AndroidDriver] u0_a172 14029 632 2511952 330684 0 0 S com.tencent.mm:tools
[AndroidDriver] Returning process name: ‘com.tencent.mm:tools’
[AndroidDriver] Found webviews: [“WEBVIEW_com.tencent.mm:tools”]
[AndroidDriver] Available contexts: [“NATIVE_APP”,“WEBVIEW_com.tencent.mm:tools”]
[AndroidDriver] Connecting to chrome-backed webview context ‘WEBVIEW_com.tencent.mm:tools’
[AndroidDriver] A port was not given, using random free port: 8000
[AndroidDriver] Before starting chromedriver, androidPackage is com.tencent.mm
[Chromedriver] Changed state to ‘starting’
[Chromedriver] Found 1 executable in ‘C:\Users\YQ\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win’
[Chromedriver] The following Chromedriver executables were found:
[Chromedriver] C:/Users/YQ/AppData/Local/Programs/Appium/resources/app/node_modules/appium/node_modules/appium-chromedriver/chromedriver/win/chromedriver.exe (minimum Chrome version ‘71.0.3578’)
[ADB] Getting package info for ‘com.android.chrome’
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell dumpsys package com.android.chrome’
[Chromedriver] Unable to discover Chrome version. Using Chromedriver 2.46 at ‘C:/Users/YQ/AppData/Local/Programs/Appium/resources/app/node_modules/appium/node_modules/appium-chromedriver/chromedriver/win/chromedriver.exe’
[Chromedriver] Set chromedriver binary as: C:/Users/YQ/AppData/Local/Programs/Appium/resources/app/node_modules/appium/node_modules/appium-chromedriver/chromedriver/win/chromedriver.exe
[Chromedriver] Killing any old chromedrivers, running: wmic process where “commandline like ‘%chromedriver.exe%–port=8000%’” delete
[Chromedriver] Successfully cleaned up old chromedrivers
[Chromedriver] Cleaning any old adb forwarded port socket connections
[ADB] List forwarding ports
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 forward --list’
[Chromedriver] Spawning chromedriver with: C:/Users/YQ/AppData/Local/Programs/Appium/resources/app/node_modules/appium/node_modules/appium-chromedriver/chromedriver/win/chromedriver.exe --url-base=wd/hub --port=8000 --adb-port=5037 --verbose
[Chromedriver] Chromedriver version: ‘2.46.628402’
[WD Proxy] Matched ‘/status’ to command name ‘getStatus’
[WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8000/wd/hub/status] with no body
[WD Proxy] Got response with status 200: “{"sessionId":"","status":0,"value":{"build":{"version":"2.46.628402 (536cd7adbad73a3783fdc2cab92ab2ba7ec361e1)"},"message":"ChromeDriver ready for new sessions.","os":{"arch":"x86_64","name":"Windows NT","version":"10.0.18362"},"ready":true}}”
[WD Proxy] Determined that the downstream protocol for proxy is MJSONWP
[WD Proxy] Matched ‘/session’ to command name ‘createSession’
[WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.tencent.mm”,“androidUseRunningApp”:true,“androidDeviceSerial”:“36c02a5”},“loggingPrefs”:{“browser”:“ALL”}}}
[WD Proxy] Got response with status 200: {“sessionId”:“cea749b7a4b752f2197f173033561be7”,“status”:13,“value”:{“message”:“unknown error: Failed to get sockets matching: @webview_devtools_remote_.*13580\n (make sure the app has its WebView configured for debugging)\n (Driver info: chromedriver=2.46.628402 (536cd7adbad73a3783fdc2cab92ab2ba7ec361e1),platform=Windows NT 10.0.18362 x86_64)”}}
[WD Proxy] Got an unexpected response: {“sessionId”:“cea749b7a4b752f2197f173033561be7”,“status”:13,“value”:{“message”:"unknown error: Failed to get sockets matching: @webview_devtools_remote_.*13580\n (make sure the app has its WebView configured for debugging)\n (Driver info: chromedriver=2.46.628402 (536cd7adbad73a3783fdc2cab92ab2…
[MJSONWP] Matched JSONWP error code 13 to UnknownError
[Chromedriver] Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*13580
[Chromedriver] (make sure the app has its WebView configured for debugging)
[Chromedriver] (Driver info: chromedriver=2.46.628402 (536cd7adbad73a3783fdc2cab92ab2ba7ec361e1),platform=Windows NT 10.0.18362 x86_64)
[Chromedriver] at Object.wrappedLogger.errorAndThrow (C:\Users\YQ\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:78:13)
[Chromedriver] at errorAndThrow (C:\Users\YQ\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:493:13)
[WD Proxy] Matched ‘/session’ to command name ‘createSession’
[WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.tencent.mm”,“androidUseRunningApp”:true,“androidDeviceSerial”:“36c02a5”},“loggingPrefs”:{“browser”:“ALL”}}}

Aleksei · October 18, 2019, 8:10am

@johny first developers should enable webView debug in app ask them

johny · October 18, 2019, 8:56am

@Aleksei I’ve opened debug mode,but still report the same error.

Aleksei · October 18, 2019, 10:34am

Iiiiii see in logs

(minimum Chrome version ‘71.0.3578’)
[ADB] Getting package info for ‘com.android.chrome’
[ADB] Running ‘D:\adt-bundle-windows\sdk\platform-tools\adb.exe -P 5037 -s 36c02a5 shell dumpsys package com.android.chrome’
[Chromedriver] Unable to discover Chrome version. Using Chromedriver 2.46 at

Update to appium 1.16 or uninstall and install appium with correct chrome driver version.

johny · October 21, 2019, 8:18am

i installed chromedriver, the version is corresponding to webview version(cause the app use it’s build-in browser core, so i haven’t install chrome browser in my device) %E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87_20191021160752 , everthing has done,but still error.

Aleksei · October 21, 2019, 8:41am

Appium installs chromedriver in it own folder.

Follow http://appium.io/docs/en/writing-running-appium/web/chromedriver/

johny · October 21, 2019, 8:56am

i’ve searched this help doc before,and did as it’s said,though i selected the proper chromedriver version and installed it,nothing difference.

johny · October 21, 2019, 9:28am

@Aleksei i know why i can’t switch webview success before, cause the word in capabilities chromeOptions, it’s first letter should be lowercase,but i wrote it as uppercase.Thanks so much.