1 回答
- 最新
- 投票最多
- 评论最多
0
Thank you for reaching out us regarding the above query. I would like to share that the issue could be Appium tried to find the activity in the app to start however that activity can't be started programmatically. So you can try the below to avoid this issue :
- set the appActivity and appPackage capabilities so that they're not automatically found by Appium.
- If that doesn't work maybe try a wildcard appPackage/Activity name like "myProject*"
- Have the developer create an intent specifically for getting past that start up screen that prompts us for a phone number. That screen I believe has a different activity than Appium's looking for.
Having said that, for deep dive on your account specific issue, please feel free to open a support case with AWS using the following link, as it would require sensitive data which cannot be requested publicly.
相关内容
- 已提问 8 个月前
AWS 官方已更新 3 年前- AWS 官方已更新 2 年前
Hi Subhayu
Despite the accurate identification of AppActivity and package by Appium, an unexpected failure occurs. Interestingly, when I manually insert the same values into the YAML file, the process works successfully.