We have an interface which we build based on user input - in this case for automation. This works fine on iOS-based devices, but on Android-based devices the page isn't built correctly.
In the page pictured below, theres a horizontal-scrolling list which has one of two different subpages added depended on the type of element we're controlling. As you can see, the iOS one displays the two different elements correctly, and also displays all the elements requested - the Android one does neither of these.
The other issue pictured is the button images - they're set via JS too, and displayed correctly in the iOS image, and not displayed (or even displayed as a text path!) in the Android one.
We have an interface which we build based on user input - in this case for automation. This works fine on iOS-based devices, but on Android-based devices the page isn't built correctly.
In the page pictured below, theres a horizontal-scrolling list which has one of two different subpages added depended on the type of element we're controlling. As you can see, the iOS one displays the two different elements correctly, and also displays all the elements requested - the Android one does neither of these.
The other issue pictured is the button images - they're set via JS too, and displayed correctly in the iOS image, and not displayed (or even displayed as a text path!) in the Android one.
Happy to provide a copy of the GUI for testing,
iOS:
Android: