-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash When Using Send Keys Endpoint #1033
Comments
Just chiming in to say that I started to experience this exact issue last week (same error on setStylusHandwritingEnabled when trying to do sendKeys). Typically it points to mismatches in the dependencies, but even after updating to match I'm getting this same error. Will continue to watch and/or update if we find any solution. Appium Version: 2.13.1
|
@KazuCocoa any thoughts on what this could be? As far as I can tell the espressoBuildConfig is matching our app's dependencies. I assume this is related to the androidx.compose.foundation:foundation version, but I've double checked with our devs and it matches. Do you have another thought as to why it would throw an error like this? |
I don't have much experience about that, but you also could try out directly modifying the gradle code: https://github.com/appium/appium-espresso-driver/tree/master?tab=readme-ov-file#running is how to build for a specific package target. Generally, dependencies and proguard optimization could cause this kind of issue. |
Crash When Using Send Keys Endpoint
Appium Version:
2.5.1
and2.13.1
Appium Espresso Driver Version:
2.44.2
and3.5.1
Android Simulator Version - Replicated on at least Android APIs 30, 33 and 34
App Used - I've created a minimal app, with a single textfield - https://github.com/BenPela/single-text-field-app
Here are my appium options and python code used to replicate the bug
Here is my log from Appium - https://gist.github.com/BenPela/74ec617e3ad768915cd144988df172b4
Key section of error message
Any ideas how to fix this, or a good alternative to entering text in fields for now?
The text was updated successfully, but these errors were encountered: