Skip to content
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

Open
KazuCocoa opened this issue May 26, 2022 · 5 comments
Open

Comments

@KazuCocoa
Copy link
Member

KazuCocoa commented May 26, 2022

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.

@jlipps
Copy link
Member

jlipps commented May 26, 2022

yes, absolutely. we should no longer require appActivity to be present since we can now determine launchable activity without it.

@vrnvorona
Copy link

Can we optionally skip launching activity at all? I want to try to run EspressoDriver and UIAutomator2Driver at the same time.

@KazuCocoa
Copy link
Member Author

No app and appActivity capabilities start a session with do nothing.

@vrnvorona
Copy link

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).

@KazuCocoa
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants