appium
Web Driver Exception for versions >2.2.0
The problem
I am finding some web driver exception when I update the python package dependency Appium Python Client to 2.7.1. PFA the screenshot of the same. It works absolutely fine for 2.2.0. Please let me know how to go about this.
Environment
- Appium version (or git revision) that exhibits the issue: v1.20.2
- Last Appium version that did not exhibit the issue (if applicable): v1.20.2
- Desktop OS/version used to run Appium: NA
- Node.js version (unless using Appium.app|exe): NA
- Mobile platform/version under test: android/10
- Real device or emulator/simulator: cloud device
- Appium CLI or Appium.app|exe: NA
Sorry, where did the java.lang.NullPointerException come from?
appium is NodeJS, so the response message should not be such Java error.
Please attache the appium server log, and relevant module logs (and more explanation about your configuration.)
@KazuCocoa This issue is for https://pypi.org/project/Appium-Python-Client/
I mean the server side log to see the actual request structure, not client itself. I guess you haven't sent a new session request to an appium directly.
The possible case is the base selenium-webdriver version update.
PFA the server side logs. But there is nothing much useful. What would be the ideal selenium webdriver version, currently it works with selenium 4.2 appiumLogsAPC2.7.1.txt
The server log did not have the request of POST /wd/hub/session, so did something exist between the attached server log's instance and the Python client to interrupt the Python client request (which returns null pointer exception?)?
Our CI has tests with latest Appium/Selenium with a server as https://github.com/appium/python-client/runs/9135002927 . Then, the selenium server might work. I wonder if the server which returns the null pointer exception was not able to parse W3C capabilities properly.
Not sure. there was nothing to interrupt the flow. Just that when updated to higher versions, showed this behaviour.
@sasasa42, you should upgrade to Appium 2 if you haven't already. Update if this issue reproduces after the upgrade.
