Recently i got M1 chip, In this I have arm64 emulator, When i run my appium code it’s not detecting webview context but it’s printing correct webview name.
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(MobileCapabilityType.NEW_COMMAND_TIMEOUT, 1000);
capabilities.setCapability("WebView.setWebContentsDebuggingEnabled", true);
capabilities.setCapability("autoAcceptAlerts", true);
capabilities.setCapability("autoDismissAlerts", true);
capabilities.setCapability("showChromedriverLog", true);
capabilities.setCapability("appium:ensureWebviewsHavePages", true);
capabilities.setCapability("appium:nativeWebScreenshot", true);
capabilities.setCapability("allowTestPackages", true);
capabilities.setCapability(MobileCapabilityType.AUTO_WEBVIEW, true);
capabilities.setCapability(MobileCapabilityType.FULL_RESET, false);
I have correct chromedriver version. 103.0.5060.53
Debug logs
debug] [W3C (c15d6220)] Calling AppiumDriver.timeouts() with args: [null,null,null,null,10000,“c15d6220-1a53-4abd-be9c-d04cd3c0ea8a”]
[debug] [BaseDriver] W3C timeout argument: {“implicit”:10000}}
[debug] [BaseDriver] Set implicit wait to 10000ms
[debug] [W3C (c15d6220)] Responding to client with driver.timeouts() result: null
[HTTP] <-- POST /wd/hub/session/c15d6220-1a53-4abd-be9c-d04cd3c0ea8a/timeouts 200 1 ms - 14
[HTTP]
[HTTP] --> POST /wd/hub/session/c15d6220-1a53-4abd-be9c-d04cd3c0ea8a/context
[HTTP] {“name”:“WEBVIEW_nz.co.noelleeming.mynlapp.qat”}
[debug] [W3C (c15d6220)] Calling AppiumDriver.setContext() with args: [“WEBVIEW_nz.co.noelleeming.mynlapp.qat”,“c15d6220-1a53-4abd-be9c-d04cd3c0ea8a”]
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Running ‘/Users/390099/Library/Android/Sdk/platform-tools/adb -P 5037 -s emulator-5554 shell cat /proc/net/unix’
[debug] [AndroidDriver] Found no active devtools sockets
[debug] [AndroidDriver] Other sockets are: [
[debug] [AndroidDriver] “0000000000000000: 00000002 00000000 00010000 0005 01 34581 @jdwp-control”,
[debug] [AndroidDriver] “0000000000000000: 00000002 00000000 00010000 0001 01 32721 @com.android.internal.os.WebViewZygoteInit/41752b32-47f9-4a38-80b1-d313bd3ff512”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0005 03 59420 @jdwp-control”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0001 03 18334 @com.android.internal.os.WebViewZygoteInit/41752b32-47f9-4a38-80b1-d313bd3ff512”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0005 03 49703 @jdwp-control”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0005 03 55612 @jdwp-control”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0005 03 72384 @jdwp-control”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0005 03 34653 @jdwp-control”,
[debug] [AndroidDriver] “0000000000000000: 00000003 00000000 00000000 0005 03 55999 @jdwp-control”
[debug] [AndroidDriver] ]
[debug] [AndroidDriver] Found 0 webviews: []
[debug] [AndroidDriver] Available contexts: [“NATIVE_APP”]
[debug] [W3C (c15d6220)] Encountered internal error running command: NoSuchContextError: No such context found.
[debug] [W3C (c15d6220)] at AndroidUiautomator2Driver.setContext (/opt/homebrew/lib/node_modules/appium/node_modules/appium-android-driver/lib/commands/context.js:51:11)
[HTTP] <-- POST /wd/hub/session/c15d6220-1a53-4abd-be9c-d04cd3c0ea8a/context 400 121 ms - 278
[HTTP]
Aug 04, 2022 5:53:35 PM org.openqa.selenium.remote.ErrorCodes toStatus
INFO: HTTP Status: ‘400’ -> incorrect JSON status mapping for ‘unknown error’ (500 expected)
io.appium.java_client.NoSuchContextException: No such context found.
Driver info: io.appium.java_client.android.AndroidDriver
Can anybody help?