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

lock -> unlock doesn't work #12

Open
rompic opened this issue Oct 21, 2014 · 2 comments
Open

lock -> unlock doesn't work #12

rompic opened this issue Oct 21, 2014 · 2 comments

Comments

@rompic
Copy link

rompic commented Oct 21, 2014

I have the impression, that the unlock mechanism doesn't work so my tests use to stop prematurely.:

2014-10-21 09:50:58 +0000 Debug: target.lockForDuration("2.00243217498064")
2014-10-21 09:51:01 +0000 Debug: target.springboard().mainWindow().scrollViews().firstWithPredicate("ANY elements.name == 'SlideToUnlock' OR ANY elements.name == 'SlideToSetup'").dragInsideWithOptions({endOffset:{x:0.90,y:0.90}}, duration:"0.5", startOffset:{x:0.10,y:0.90}}})
2014-10-21 09:52:18 +0000 Stopped: Script was stopped by the user

Anyone experiencing similar issues?

@skrach
Copy link

skrach commented Feb 17, 2015

Yes I'm experiencing the same problem.

The device screen is locked by UIATarget.lockForDuration(). This method successfully locks the screen but fails to unlock it after the specified time has passed. Since CrashMonkey is using UI Automonkey, the following issue may be of interest: jonathanpenn/ui-auto-monkey#11

@skrach
Copy link

skrach commented Feb 17, 2015

The problem can be mitgiated by providing a custom json config which doesn't include the lock event. A sample config can be found in Pull Request #13

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

2 participants