This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Apr 2018
10 / 10
Apr 2018
Apr 2018
Liru
Apr '18

Hi everyone,

I’m starting to add Appium test to an aplicattion. The application is made in cordova and I’m having issues with my first test that will click a button to make login.
The connection with my phone is working but at the time that Appium have to execute my first test, it crashes with the following error ->

Captura
Captura.PNG1498x270 25.3 KB

I’m getting the id from the browser inspector like this ->

Captura
Captura.PNG991x399 69.8 KB

What i’m doing wrong?

Thanks in advance!! :slight_smile:

  • created

    Apr '18

  • last reply

    Apr '18
  • 9

    replies

  • 735

    views

  • 6

    users

  • 2

    likes

  • 2

    links

pushpank
Apr '18

element which you finding is not visible on screen, you can increase implicit wait time

Liru
Apr '18
pushpank

I have just tried to put a thread before the clic, but it seems to give me the same error :S in the screeen of the device the button is visible but the code doesn’t seems to find it.

Code with Thread or driver.manage()->
Captura

Same error (In error I can see that the time that the time t tried is alway the same, I’m making the thread or manage incorrectly?)->

Captura2
Captura2.PNG1537x442 45.1 KB

Liru
Apr '18
wreed

I tried with the code you have given to me and the error still remains, in pushpank reply I post an explication.

langme
Apr '18

i have the same problem with my native android app, sometimes appium doesn t find element even if the element is displayed.

Cauthon
Apr '18

You could try waiting until the element is enabled instead of displayed. I’ve had better luck using that as an explicit wait condition.

wreed
Apr '18
Liru

Have you tried increasing the time? I usually set some crazy long time (like 60 seconds) for POC since implicit wait polls and thus stops the timer once element is found. Later I go back and fine tune, but I always leave a buffer. The app I’m working on right now has 10 seconds of animation before the first screen is presented. I therefore implicitly wait for 20 seconds, and I think the elements are found in 11-12 seconds on average for that particular screen.

Gunjan_Gupta
Apr '18

Since your mobile app is built in Cordova .
It generate a webview/HTML inside a native context.
As I can see the ID is given at ‘ons-button’ Tag .
And Cordova generate a child HTML component inside this tag .
You need to traverse to the child element insiDe ‘ons-button’ either through xpath or any other locator and then click .
Then it should work.

pushpank
Apr '18
Liru

Try to add more wait with explicit wait like in blow code given 200sec and also try with change locator my it work

WebDriverWait wait = new WebDriverWait(driver,200); wait.until(ExpectedConditions.visibilityOfElementLocated(By.id(“ABCl”)));