mdberryh
commented
1 year ago I wanted to add that I tried a python client with the same running appium server, and it worked perfectly. This tells me the appiumV2 server is working fine. It is something in the chain that C# side is using....or a setting not set on my side.
for those interested here is the python code to just try it out.
from appium import webdriver
from appium.options.android import UiAutomator2Options
from appium.webdriver.common.appiumby import AppiumBy
options = UiAutomator2Options()
options.platformVersion = '12'
# Appium1 points to http://127.0.0.1:4723/wd/hub by default
driver = webdriver.Remote('http://127.0.0.1:4723', options=options)
print("checking contexts")
print(driver.contexts)
webview = driver.contexts[1]
driver.switch_to.context(webview)
# ...
driver.switch_to.context('WEBVIEW_com')
#driver.switch_to.context('NATIVE_APP')
elementsList = driver.find_elements(AppiumBy.XPATH, "//*");
print(elementsList[0])
obj = elementsList[0]
print(obj.__dict__)
print(dir(obj))
for elem in elementsList:
print(elem.text)
if elem.text =='Click to Play!':
elem.click()
mykola-mokhnach
Dor-bl
Description
I used npm to set up appium@next, which is appiumV2. I am also using the Appium dot net SDK 5.3 beta version. I am able to use native contexts, but I cannot switch to a "WEBVIEW" due to the error:
[Chromedriver@a04e] invalid argument: cannot parse capability: goog:chromeOptions [Chromedriver@a04e] from invalid argument: unrecognized chrome option: AcceptInsecureCertificates
appiumserverlogs_error.log
Environment
Details
Please provide more details, if necessary.
Code To Reproduce Issue [ Good To Have ]