-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
reset() breaks Appium if the App has been launched with "no_reset=true" #5756
Comments
I'm unable to reproduce this on 1.4.13 - can you please try a more recent version of Appium? |
first of all sorry for the late response. I spent quite some time wondering why this happens and I think this might be because of how the Could you explain the meaning of the
(if
|
@scottdixon are you able to comment the above? Or is the "how it should work" a mystery also for you? :-) |
closing this is probably the right move, but it would still be good to know how it should work - i.e. answer my last comment, because the documentation does not give the answers... |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Executing
reset()
causes appium to throw an exception if the app has been launched with"noReset":true
, but it works fine with"noReset":false
.The failing one tries to do
info: [debug] Running old fashion reset (reinstall)
and throws anerror: Problem calculating md5: TypeError: Arguments to path.resolve must be strings
errorThe working one does
info: [debug] Running fast reset (stop and clear)
Logs from the failing one (starting phone app on Galaxy S5 and resetting it)
The text was updated successfully, but these errors were encountered: