can't get anything to run

[malkomalko]

I followed the instructions to a T and set it up with tuneup. It builds fine but nothing is run inside of my tests. Even a blank test with UIALogger.logMessage("Turn on edit mode") logs out nothing.

Any ideas? I'm on IOS7/Xcode5

http://cl.ly/image/271j2Y3m2I0S

[LiamInJapan]

I'm getting the same behaviour here too - it just seems to freeze at example.js

[marcammann]

I had the same issue. What was causing the issue was that the unix_instruments.sh was getting stuck and blocking the resource. First it was that the .app couldn't be found because it had a whitespace and also instruments required a password to work. Both alerts were not visible on screen unless I minimized all windows..

[jrnk]

+1

Freezes for me too sometimes after "Build Successful!", no dialogs for a password. Only rebooting helps but it will hang eventually again after a while.
--verbose mode doesn't say anything more unfortunately.

[listrophy]

😦 I'm sorry to say that because of the way we have to interact with instruments, sometimes a very low-level thing in the OS gets screwed up (a tty/pty pair never gets released). Unless I'm mistaken, the best/easiest way to fix is to reboot.

Obviously not ideal, but I'm open to suggestions to fix. I have an open bug report with Apple so that we don't have to use the tty/pty pair, but it's languishing.

[otusweb]

Would be great if a timeout where bwoken get hung up could be added so a message could be displayed in the terminal stating a reboot might be required

[ryanjm]

I think this is the same issue as #56 (and can be closed when that one gets closed).