org.openqa.selenium.InvalidArgumentException: Parameters were incorrect. We wanted {"required":["text"]} and you sent ["id","value"]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Description
I am totally puzzled. I got a new M1 Mac laptop and believe I am using all the identical versions of the required tools as my old laptop, but I am getting org.openqa.selenium.InvalidArgumentException: Parameters were incorrect. We wanted {"required":["text"]} and you sent ["id","value"]. This occurs when I call setValue("xxx") on a text entry field.
Environment
- Java client build version 7.6.0. I have tried different versions of java but currently using 1.8.
- Appium server version v2.0.0-beta.25 (REV 552db40622bb7a82d9c6d67d2d6bcf3694b47e30)
- Desktop OS/version Apple M1, Ventura 13.2.1
- Node.js version 18.9.0
- Mobile platform/version under test: both ios 15.6.1 and android 9
- Device drivers: - xcuitest@4.19.1 [installed (NPM)], uiautomator2@2.0.1 [installed (NPM)]
- Real device or emulator/simulator: Real devices
Details
The error occurs on both Android and iOS. I have tried the most recent version of the appium server. I have tried different versions of the drivers. I have tried different versions of node. I have tried different versions of java. One big mystery is that for a brief time, I did get things to work. That occurred when I downgraded node to be the same as the version on my old laptop. But something changed in my world and things have returned to the error listed above and I am at a loss as to what to do.
Seems like a java client and server compatibility issue. Something happened like this ages ago with the python client. I don't know how this is possible, but the only difference I am seeing is that I am running things on my new M1. Hopefully, I am missing something.
Code To Reproduce Issue [ Good To Have ]
field.setValue("value")
Exception Stacktraces
Here is the application call stack
Link To Appium Logs
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal reproduction, field.setValue("value"), using the listed Java client, server, driver, Node.js, Android, and iOS versions. Compare the application call stack and Appium server log linked in the issue to isolate the client/server or driver mismatch. Done means identifying a reproducible compatibility cause and documenting the affected versions and resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100