Repository navigation
driver.lockScreen() not working as expected. #315
Description
Quoting from SO-35223434-
We have called driver.lockScreen(20); in my test followed by Runtime.getRuntime().exec("adb shell input keyevent 26"); to unlock screen. But the problem is the device is not getting locked for 20 sec. The next statement keyevent 26 is unlocking the device as soon as device is locked. So why we are providing 20 sec parameter?
Looking further into this, the AppiumDriver.java has this to say :
/** * Lock the device (bring it to the lock screen) for a given number of * seconds * * @param seconds * number of seconds to lock the screen for */ public void lockScreen(int seconds) { execute(LOCK, ImmutableMap.of("seconds", seconds)); }
Activity
TikhomirovSergey commentedon Feb 7, 2016
I will try to reproduce. But it can be the server-side problem.
TikhomirovSergey commentedon Feb 7, 2016
It is the server side problem.
appium/appium#6077
namannigam-zz commentedon Feb 7, 2016
@TikhomirovSergey there's definitely some issue with the
lockScreen()but just to clear the appium/appium#6077 depicts that the screen remains locked. While in our case the screen does not remain lock for the specified sleep time.TikhomirovSergey commentedon Feb 7, 2016
I'm searching for the cause of this problem. It is already reported probably. I've asked the question at team chat.
imurchie commentedon Feb 9, 2016
Talking this over, this appears to be the desired behavior. The locking-waiting-unlocking is necessary for iOS, where it is the only way to do any locking. For Android it should just lock. If you want it to unlock, you can call unlock.
I am making the seconds parameter optional, and documenting this difference.
Merge pull request #318 from TikhomirovSergey/master