Currently, the "initial page" feature only supports page classes that specify the @PageUrl annotation. To support mobile application automation, this feature needs to be expanded to handle Android "activity" specifications. I don't know if "current activity" information is directly accessible from the application. This would be required to extend landing page verification/synchronization to Android application page models.
It doesn't appear that the iOS UI automation frameworks provide a mechanism for direct navigation.
Currently, the "initial page" feature only supports page classes that specify the
@PageUrlannotation. To support mobile application automation, this feature needs to be expanded to handle Android "activity" specifications. I don't know if "current activity" information is directly accessible from the application. This would be required to extend landing page verification/synchronization to Android application page models.It doesn't appear that the iOS UI automation frameworks provide a mechanism for direct navigation.