Page 1 of 1

In-app webview

Posted: Mon Nov 18, 2013 11:57 am
by eafojas
Hello,

I made a very simple iOS app where there is just a webview that loads google.com. I made a recording that touches that search field and then inputs sa search value then press search button (via keyboard). When i run my recording, ranorex manages to set the value of the textfield but can't continue on with pressing enter key. The error was device communication timed-out, I've tried it several times but I still get the same result. I' using iOS 7 with ranorex v 4.1.2.161. Thanks!

Re: In-app webview

Posted: Tue Nov 19, 2013 3:38 pm
by Support Team
Hello eafojas,

Thank you for the report file.
Can you please try to increase the search timeout?
I can see in your report that you execute the 'Set Value' action on the 'VoyagerRanorexWebViewTest.LstIb' element, but the keyboard '{ENTER}' action is executed on the 'VoyagerRanorexWebViewTest.UIWindow'.
Maybe you are using the wrong Repository element.
Can you please post a Ranorex Snapshot file?

Regards,
Bernhard

Re: In-app webview

Posted: Wed Nov 20, 2013 9:56 am
by eafojas
Hello Bernhard!

Thank you for your reply! I see that the element that I used was a UIWindow and I think you a right that I was using the wrong element. But the problem is that I want to search using the iOS keyboard's "Enter/Search" button after I set the value of the search field. Based on my understanding, correct me if I'm wrong, the setValue instruction does not display the keyboard of the device, so I think that's the reason why ranorex can't find the UIKBKeyView ("Search/OK" button of the keyboard, I got its ranoreXpath using spy). Is my assumption correct? Should I just use the search button in the web view rather than the "Search/OK" button of the keyboard? I'm just trying to know the limitations with regards to in-app webViews. Thank you very much!! :D

I attached the snapshot and report of my application. Again thank you for your time! :D

Regards,
Edgar

Re: In-app webview

Posted: Thu Nov 21, 2013 5:36 pm
by Support Team
Hello Edgar,

Yes, you are correct.
A workaround is to add a touch action on the 'VoyagerRanorexWebViewTest.LstIb' element before the keyboard {ENTER} action. If you do this, the keyboard should appear and the {ENTER} button should be found.

Regards,
Bernhard