UIATargetHasGoneAWOLException

Originator:listrophy
Number:rdar://11168782 Date Originated:4/2/2012
Status:Closed Resolved:
Product:Developer Tools Product Version:instruments 1.0
Classification:Crash/Hang/Data Loss Reproducible:Sometimes
 
Summary:

Using CLI instruments, I'll sometimes encounter an error as the app is loading.

Steps to Reproduce:

From the command line, run:

$ instruments         -D /Users/brad/dev/ios/TravisCI/integration/tmp/trace         -t /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Instruments/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate         /Users/brad/dev/ios/TravisCI/build/TravisCI.app         -e UIASCRIPT /Users/brad/dev/ios/TravisCI/integration/tmp/javascript/iphone/iphone.js -e UIARESULTSPATH /Users/brad/dev/ios/TravisCI/integration/tmp/results

Expected Results:

See the UIAutomation script run correctly.

Actual Results:

Full output:

2012-04-02 15:40:45.856 instruments[14421:1203] Automation Instrument ran into an exception while trying to run the script.  UIATargetHasGoneAWOLException
2012-04-02 20:40:45 +0000 Fail: An error occurred while trying to run the script.
<instruments hangs at this point, requiring a Ctrl-C. In addition, the simulator shows a black screen with statusBar showing>

Regression:

Notes:

No insight as to what causes this, but once it occurs, it keeps occurring. Not sure if a reboot fixes it. The application being run through instruments is TravisCI.app, found at https://github.com/bendyworks/TravisCI.app/tree/tuneup_js

Comments

workaround confirmed for me too

I came here given the same error, and disconnecting a connected iPhone and retrying the test with a fresh iOS simulator (the simulator app closed) freshly launched the iOS simulator and did proceed to run successfully from the command line, my UIAutomation script.

By sohail at Sept. 2, 2012, 9:39 p.m. (reply...)

Duplicated as 11363395

By heath.borders at May 2, 2012, 3:09 p.m. (reply...)

update: now reproducible

I can now reproduce at will. I believe the conditions are:

  • Connect an iPhone to your development machine
  • Use instruments from the CLI to run an Automation test in the simulator

To workaround, disconnect the iPhone and retry the test.

By listrophy at April 25, 2012, 11:16 p.m. (reply...)

update

This seems to happen when the host operating system (Lion, in my case) neglects to ask that (paraphrased, since difficult to reproduce) "Developer tools needs access to another process."

How to cause it to ask or not ask is beyond my ken, but I'm certain the dialog isn't simply behind other windows.

By listrophy at April 12, 2012, 5:50 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!