Closed itkhanz closed 1 year ago
@itkhanz set the automationName as 'XCuiTest'
Thanks. Setting it to XCuiTest solved the issue. I thought the automationName capabilities are case-insensitive and earlier I had it set as XCUITEST (in Capital case)
return new XCUITestOptions()
.setAutomationName("XCUITEST")
.setPlatformName("iOS")
In the documentation https://appium.github.io/appium-xcuitest-driver/4.32.5/capabilities/ , it also states that Values of automationName are compared case-insensitively.
Shouldn't this equality check be made case-insensitive in the source code of plugin?
@itkhanz Fixed in version 2.0.0. Please check the readMe. we have contract changes.
Hi, I was working with appium-wait-plugin for past few days and it was working fine but today to my surprise it stopped working. I even restarted the appium server and simulator with fullReset but it did not solve the issue. Further i also ran the following commands as suggested on some forums to clear any other sessions running.
But trying all of these did not solve the issue. If I run my script without the wait plugin, then it works successfully. I have the following environment setup:
Java Client Test Code for UIKitCatalogApp:
i get the following error at findElement call: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Cannot read properties of undefined (reading 'jwproxy')
Here are the appium server logs. I am also attaching the logs. appiumlogs.txt
What I have observed is that session is created successfully and app is launched but the script fails at the findElement because of the wait-plugin. Command 'findElement' was not handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command was handled by these: ["element-wait"]. Encountered internal error running command: TypeError: Cannot read properties of undefined (reading 'jwproxy')_
As you can see in the logs response that the error is caused because of the following reasons:
Could you please look into this issue what may be causing this problem?