java-client
java-client copied to clipboard
Double Tap & double click doesn't working in both java and python android platform
The problem
I write the test script code for WECHAT APPLICATION group chat message to get the text message element from the double tab but it's not performing double tap on the screen. Actually I want to twice click on similar element because when element double tap/double click then text will be shown in complete screen. That's issue I'm facing in our the appium project; I tell you below my project environment specifications;
Environment
- Appium version (or git revision) that exhibits the issue: Version Appium 1.17.1
- Desktop OS/version used to run Appium:1.17.1
- Node.js version (unless using Appium.app|exe):
- Npm or Yarn package manager: NPM
- Mobile platform/version under test: Android 9 & 10
- Real device or emulator/simulator: REAL DEVICE
- Appium CLI or Appium.app|exe: APPIUM APP
Details
If necessary, describe the problem you have been experiencing in more detail.
Link to Appium logs
Create a GIST which is a paste of your full Appium logs, and link them here. Do NOT paste your full Appium logs here, as it will make this issue very long and hard to read! If you are reporting a bug, always include Appium logs!
Code To Reproduce Issue [ Good To Have ]
String path = "//android.widget.RelativeLayout[@index='" + index + "']//android.view.View[@long-clickable='true']"; AndroidElement e = this.driver().waitUtilElementVisible(path, 2);
TouchActions actions = new TouchActions(this.driver().instance);
actions.doubleTap(e);
actions.perform();
- Please provide the full server log.
- Try to use W3C actions instead
[W3C (879626c9)] Responding to client with driver.findElement() result: {"element-6066-11e4-a52e-4f735466cecf":"8b037606-c2c8-4c9a-b3f8-6119e373899d","ELEMENT":"8b037606-c2c8-4c9a-b3f8-6119e373899d"}
On Mon, Aug 3, 2020 at 4:30 PM Mykola Mokhnach [email protected] wrote:
- Please provide the full server log.
- Try to use W3C actions instead
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/appium/appium/issues/14617#issuecomment-667886679, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFZ43KO3DHTOZ2OB63LFCH3R6ZYRNANCNFSM4PTCL5FA .
java.lang.ClassCastException: class io.appium.java_client.android.AndroidDriver cannot be cast to class org.openqa.selenium.interactions.HasTouchScreen (io.appium.java_client.android.AndroidDriver and org.openqa.selenium.interactions.HasTouchScreen are in unnamed module of loader 'app')
On Mon, Aug 3, 2020 at 4:40 PM Haider Ali [email protected] wrote:
[W3C (879626c9)] Responding to client with driver.findElement() result: {"element-6066-11e4-a52e-4f735466cecf":"8b037606-c2c8-4c9a-b3f8-6119e373899d","ELEMENT":"8b037606-c2c8-4c9a-b3f8-6119e373899d"}
On Mon, Aug 3, 2020 at 4:30 PM Mykola Mokhnach [email protected] wrote:
- Please provide the full server log.
- Try to use W3C actions instead
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/appium/appium/issues/14617#issuecomment-667886679, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFZ43KO3DHTOZ2OB63LFCH3R6ZYRNANCNFSM4PTCL5FA .