how to cast MobileElement to IOSElement

[aznime]

Recently updated to latest 2.2.0 but this piece of code fails due to setValue() being moved to IOSElement.

        if (driver instanceof IOSDriver) {
            element.setValue(value)   // element is of MobileElement
        } else if (driver instanceof AndroidDriver) {
            element.sendKeys(value)
        }

Any ideas on how I can get it to work with the latest java-client?

Thanks in advance.

[TikhomirovSergey]

Hi @aznime !

       if (driver instanceof IOSDriver) {
          /*(!!!)-->*/  ((IOSElement) element).setValue(value)   // element is of MobileElement
        } else if (driver instanceof AndroidDriver) {
            element.sendKeys(value)
        }

Also I can advice you this combination of actions:

       element.clear();
       element.sendKeys(value)

It should work against both Android and iOS.

[aznime]

Thanks. I tried to cast it like that but got an exception. I think it's due to the fact that my driver is of AppiumDriver and the element is MobileElement. They're not specific to either iOS nor Android.

I'll revert to the earlier version for now as it's nice to use setValue() for IOS as it is much faster than sendKeys().

[Jonahss]

What is the exception you got?

On Wed, Apr 15, 2015 at 5:36 PM, Philip Tran notifications@github.com
wrote:

Thanks. I tried to cast it like that but got an exception. Would be nice
to use setValue() for IOS as it is much faster than sendKeys() though

—
Reply to this email directly or view it on GitHub
#185 (comment).

[aznime]

Below is the exception:

org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '[[IOSDriver: iOS on MAC (f8d4539c-2845-4aa8-b4c1-d02f474e399c)] -> accessibility id: Register:FormField:Email:TextField]' with class 'io.appium.java_client.MobileElement$$EnhancerByCGLIB$$f164cb9c' to class 'io.appium.java_client.ios.IOSElement'

[TikhomirovSergey]

Now it is clear. You are using PageFactory and it is a proxy of an element.
I can consider it a bug and I know how to fix it.

[aznime]

Thank you!

[TikhomirovSergey]

@aznime Hi. It has been fixed. Please look above. Thanks for the bug report :) It is suposed to be included in the next release.