Comment 1 for bug 1238298

I'm not able to reproduce the stack traces on my local system, but I do see that the screen often does not come up at the start of a test run.

Inspection of the device shows a unity8 crash occurring during the unlock_screen code. But unity8 was coming up with "-testability". Eventually, I was able to get a more reliable environment by inserting a delay in the unlock between the unity8 restart and the actual swipe.