You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the following class (We have a base screen class that is used for Android and iOS that each specify T as AndroidElement and IOSElement, respectively, where we want to retain the specific platform element type):
PageFactory.initElements(newAppiumFieldDecorator(driver),
newScreenWithLists<MobileElement>()); // Or AndroidElement or IOSElement
The "listT" field does not get initialized as it fails the isDecoratableList check in AppiumFieldDecorator's DefaultFieldDecorator implementation when checking the list's type is one of "availableElementClasses".
Environment
appium java client build version: 6.1.0
selenium client build version: 3.12
Details
This generic type may be able to be checked with an additional bounds check in AppiumFieldDecorator's isDecoratableList:
Description
Given the following class (We have a base screen class that is used for Android and iOS that each specify T as AndroidElement and IOSElement, respectively, where we want to retain the specific platform element type):
and initialization with:
The "listT" field does not get initialized as it fails the isDecoratableList check in AppiumFieldDecorator's DefaultFieldDecorator implementation when checking the list's type is one of "availableElementClasses".
Environment
Details
This generic type may be able to be checked with an additional bounds check in AppiumFieldDecorator's isDecoratableList:
Testing
https://github.com/appium/java-client/blob/master/src/test/java/io/appium/java_client/pagefactory_tests/GenericTest.java
could update the Supplier to:
Related issue:
#368
Code To Reproduce Issue [ Good To Have ]
The text was updated successfully, but these errors were encountered: