-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can appActivity blank by https://github.com/appium/appium-adb/pull/599 #528
Comments
yes, absolutely. we should no longer require appActivity to be present since we can now determine launchable activity without it. |
Can we optionally skip launching activity at all? I want to try to run EspressoDriver and UIAutomator2Driver at the same time. |
No app and appActivity capabilities start a session with do nothing. |
I thought from docs that appActivity is required if paired with appPackage (which I need for appium to recognize my id's). |
Sorry I missed appPackage. no app, or no appActivity and appPackage, then an appium session starts without starting any activities. Although our general expected use case is with app, or with appActivity and appPackage, and start them in a new session request. |
just a working memo.
WIth appium/appium-adb#599, maybe we can get rid of appActivity name as a mandatory parameter from uia2 capabilities. If it was blank, we can set the default launchable activity.
The text was updated successfully, but these errors were encountered: