-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
Why am I required to do manually when before I didn't need to? #501
Comments
It is not required, no. It's not clear that there is a bug. Make sure you have the latest version of Appium 2 and then try this with your device connected to clear everything out and upgrade the driver to the latest version:
|
Hello @jlipps, Thanks for the reply. Here is the output of those commands: $ appium driver run uiautomator2 reset ======= $ appium driver update uiautomator2 |
ok, try the latest uiautomator2 driver. it was not correctly exporting the reset script before. |
Hello!
2 months or so ago I had managed to setup appium + UIAutomator2. I just needed to install the driver (via NPM) and everything magically worked.
Today, I spent a few hours trying to understand why I kept getting the following error:
I managed to fix it by downloading this repository and following its steps (gradle clean assemble + manually install the 2 apks).
My question is: why is this now required for the automation to work when before all was nice and easy?
Also, I was planning to use appium and Browserstack but if I wouldn't be able to install the 2 apks manually every time. So, I must find a better solution.
Is this a bug somewhere else or is the new "workflow"?
The text was updated successfully, but these errors were encountered: